feat: automated backport robot and /test command #14147
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Part of #12592
Motivation
Maintaining released versions of argo-workflows is not automated. This will help by allowing the backporting of commits as they are merged rather than by the release manager at the time of release.
Each PR can be CI tested independently then, and only those that pass get merged.
Modifications
Enabled CI on release branch PRs.
Added a new backport action, triggered on
closedPRs and comment creation. This useskorthout/backport-actionto do the backport. After considering various canned actions this was chosen as it does a decent job, and many others are unmaintained.nixpkgsuses this action, and as one of the most prolific repos it seemed prudent to follow.backport/<branchname>to match our other labels.We would need to add labels
backport/release-3.5andbackport/release-3.6to allow this to be used.Verification
I have setup my fork to run this and done some merges there and then asked the action to backport them.
Documentation
Added documentation for how to use the labels,
/backportand/test, and for the other comment based command which already existed/retest