-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
📖 WIP - Proposal: Automated Kubebuilder Project Update Action #4302
base: master
Are you sure you want to change the base?
📖 WIP - Proposal: Automated Kubebuilder Project Update Action #4302
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: camilamacedo86 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 |
I would like to help in this one 😄 I am trying to use a similar approach in one of the projects I work on https://github.com/migtools/oadp-non-admin/blob/master/docs/CONTRIBUTING.md#upgrade-kubebuilder-version But on other project, the upgrade process does not have any guidelines, and we are very outdated on current features. This would facilitate the project being up to date with lastest kubebuilder releases |
Regards: #4302 (comment) That would be great. We also need to ensure that we have a test in place to ensure this solution |
de211ef
to
7e41838
Compare
Proposal: Automated Kubebuilder Project Update Action
This proposal aims to create a GitHub Action similar to Dependabot for Kubebuilder,
automating the process of regenerating scaffolds and preserving custom code when new
versions of Kubebuilder are released. This solution ensures that projects stay
updated with best practices, bug fixes, and features, ultimately improving
maintainability and adoption by reducing the complexity of manual updates.