-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor(images/autobump): make bump of component and config optional #999
Conversation
Signed-off-by: Massimiliano Giovagnoli <me@maxgio.it>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: maxgio92 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Issues go stale after 90d of inactivity. Mark the issue as fresh with Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with Provide feedback via https://github.com/falcosecurity/community. /lifecycle stale |
Hi @leogr, no worries. I think we should close this in favor of the new autobumper. @cappellinsamuele working on that already :) And #1132 will definitely superseed this. WDYT? |
Ok, for me! I just wanted to sort this out 😺 |
Given that autobump script is no more existent, is this still needed? |
You're right, totally agree @FedeDP, thank you. /close |
@maxgio92: Closed this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This PR allows to autobump components and Prow config separately.
For example it could be bumped a Peribolos job only, without the requirement of having Prow config in place.