Upstream remote branch naming for repositories, etc. - #10
Open
marcmengel wants to merge 10 commits into
Open
Conversation
Collaborator
Author
|
This is actually branched off of local_bootstrap / PR 9. it will look much smaller once that is merged. |
gartung
approved these changes
Aug 5, 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
2 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.
The previous naming of the repository remotes was unhelpful when folks wanted to update recipe repositories;
the copy in the upstream instance was listed as "origin" its "origin" remote was addes as "upstream_origin".
Now we set our origin to the same as the upstream's and make the reference to the upstreams copy named "upstream" .