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
contrib: Explicitly set remote for backport branches #16804
Merged
Merged
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
Before this change, the backporting scripts would correctly push to the user's remote, but the default remote for the backport branch was left as origin (typically cilium/cilium). This commit sets the backporting branch's remote to the user's remote, so further pushes from the command line (e.g. after adding more commits or rebasing) go by default to the correct remote. Signed-off-by: Tom Payne <tom@isovalent.com>
twpayne
added
the
release-note/misc
This PR makes changes that have no direct user impact.
label
Jul 6, 2021
I've added the |
qmonnet
approved these changes
Jul 6, 2021
installation-and-connectivity test failure is likely cilium/cilium-cli#367. |
Marking this as |
twpayne
added
the
ready-to-merge
This PR has passed all tests and received consensus from code owners to merge.
label
Jul 7, 2021
maintainer-s-little-helper
bot
moved this from Needs backport from master
to Backport pending to v1.10
in 1.10.3
Jul 8, 2021
maintainer-s-little-helper
bot
moved this from Backport pending to v1.10
to Backport done to v1.10
in 1.10.3
Jul 15, 2021
This was referenced Jul 15, 2021
maintainer-s-little-helper
bot
moved this from Needs backport from master
to Backport pending to v1.9
in 1.9.9
Jul 15, 2021
maintainer-s-little-helper
bot
moved this from Needs backport from master
to Backport pending to v1.8
in 1.8.11
Jul 15, 2021
maintainer-s-little-helper
bot
moved this from Backport pending to v1.9
to Needs backport from master
in 1.9.9
Jul 19, 2021
maintainer-s-little-helper
bot
moved this from Backport pending to v1.9
to Needs backport from master
in 1.9.9
Jul 19, 2021
maintainer-s-little-helper
bot
moved this from Backport pending to v1.8
to Backport done to v1.8
in 1.8.11
Jul 22, 2021
joestringer
moved this from Needs backport from master
to Backport done to v1.9
in 1.9.10
Sep 1, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
ready-to-merge
This PR has passed all tests and received consensus from code owners to merge.
release-note/misc
This PR makes changes that have no direct user impact.
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.
Before this change, the backporting scripts would correctly push to the
user's remote, but the default remote for the backport branch was left
as origin (typically cilium/cilium).
This commit sets the backporting branch's remote to the user's remote,
so further pushes from the command line (e.g. after adding more commits
or rebasing) go by default to the correct remote.
Signed-off-by: Tom Payne tom@isovalent.com