-
Notifications
You must be signed in to change notification settings - Fork 66
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
Wg/rel/only backport to v x.x.x branch #112
Closed
DaedalusG
wants to merge
12
commits into
tibdex:main
from
sourcegraph:wg/rel/only-backport-to-vX.X.x-branch
Closed
Wg/rel/only backport to v x.x.x branch #112
DaedalusG
wants to merge
12
commits into
tibdex:main
from
sourcegraph:wg/rel/only-backport-to-vX.X.x-branch
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
…ils (#2) When backporting fails it doesn't add the generic backports label this should resolve that to be able to capture all backport PR's
This change automatically adds a GitHub Action run link in the comment section upon job failure, making it easier and quicker for devs to troubleshoot why their PR backports are failing. relates to: https://sourcegraph.slack.com/archives/C04MYFW01NV/p1687195586357239
This is to help the release guild in the loop for every backported PR. Not yet a perfect solution because this only works for automatically backported PRs, but at least an improvement.
… manual backport (#5)
the current experience is quite bad when you run into conflict, I prefer to have commands I can just copy and paste to resume the process post-creation step is easy to miss, i.e., remove `release-blocker` label https://github.com/sourcegraph/sourcegraph/pull/56448#issuecomment-1711833003
Remove test plan comment from backported PRs
remove mention of release guild
This PR further simplifies how we display failed backport messages and gives alternative options to creating manual backports. [#60489](https://github.com/sourcegraph/sourcegraph/pull/60489) added the backport functionality to the `sg` tool. | BEFORE | AFTER | |---|---| |  | <video src="https://github.com/sourcegraph/backport/assets/25608335/a90ad1f9-d612-4f09-9f10-dad84b94a844" width="320" height="240" controls></video> |
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.
This enforces the new release process by limiting the
backport-*
label/github action from firing except for releases labeled likebackport-5.4.x
orbackport-5.3.x