-
Notifications
You must be signed in to change notification settings - Fork 13
Commit
) This is an automatic backport of pull request #300 done by [Mergify](https://mergify.com). Cherry-pick of 511e534 has failed: ``` On branch mergify/bp/kubectl-v26/main/pr-300 Your branch is up to date with 'origin/kubectl-v26/main'. You are currently cherry-picking commit 511e534. (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) Changes to be committed: modified: .gitattributes modified: .gitignore new file: .gitpod.yml modified: .projen/deps.json modified: .projen/files.json modified: .projenrc.ts modified: CONTRIBUTING.md modified: package.json modified: yarn.lock Unmerged paths: (use "git add <file>..." to mark resolution) both modified: API.md both modified: test/kubectl-layer.integ.snapshot/lambda-layer-kubectl-integ-stack.assets.json both modified: test/kubectl-layer.integ.snapshot/lambda-layer-kubectl-integ-stack.template.json ``` 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
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.