Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
build: add initscripts, coreutils-common and vim for developers usage…
… (backport #58) (#59) This is an automatic backport of pull request #58 done by [Mergify](https://mergify.com). Cherry-pick of 1641fd1 has failed: ``` On branch mergify/bp/release_2.0/pr-58 Your branch is up to date with 'origin/release_2.0'. You are currently cherry-picking commit 1641fd1. (fix conflicts and run "git cherry-pick --continue") (use "git cherry-pick --skip" to skip this patch) (use "git cherry-pick --abort" to cancel the cherry-pick operation) Unmerged paths: (use "git add <file>..." to mark resolution) both modified: Dockerfile no changes added to commit (use "git add" and/or "git commit -a") ``` To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally --- <details> <summary>Mergify commands and options</summary> <br /> More conditions and actions can be found in the [documentation](https://docs.mergify.com/). You can also trigger Mergify actions by commenting on this pull request: - `@Mergifyio refresh` will re-evaluate the rules - `@Mergifyio rebase` will rebase this PR on its base branch - `@Mergifyio update` will merge the base branch into this PR - `@Mergifyio backport <destination>` will backport this PR on `<destination>` branch Additionally, on Mergify [dashboard](https://dashboard.mergify.com/) you can: - look at your merge queues - generate the Mergify configuration with the config editor. Finally, you can contact us on https://mergify.com </details>
- Loading branch information