Automate release PRs to r/r repo#135
Open
mallardduck wants to merge 3 commits into
Open
Conversation
…R creation logic for Rancher.
mallardduck
force-pushed
the
rancher-pr-workflows
branch
from
6dbfb4a to
68a882a
Compare
briandowns
reviewed
Jul 9, 2026
|
|
||
| # Fetch and checkout target branch | ||
| if ! git -C "$RANCHER_DIR" fetch "$RANCHER_REMOTE" "$TARGET_BRANCH" 2>&1; then | ||
| summary " ⚠️ Failed to fetch branch \`$TARGET_BRANCH\` - skipping" |
Contributor
There was a problem hiding this comment.
Unless other projects across our realm of responsibility use these emojis, I'd say get rid of them.
diogoasouza
approved these changes
Jul 10, 2026
This file contains hidden or 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
3 participants
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.
This PR automates the creation of PRs to
r/rrepo when we tag a stable release.This does not automate non-stable releases as not all unstable tags need to be "shipped". This reduces the noise that automations creating PRs can cause if the PRs are not desired. As a happy compromise we can manually trigger the "Push to Rancher" workflow with a specified tag for PRs to be generated.