How the GitHub CLI can now enable triangular workflows (github.blog)

submitted 1 month ago* (last edited 1 month ago) by [email protected] to c/[email protected]

5 comments fedilink hide all child comments

For those familiar with Git terminology:

The simplest way to assemble a triangular workflow is to set the branch’s merge key to a different branch name, like so:
[branch “branch”]
   remote = origin
   merge = refs/heads/default
This will result in the branch pullRef as origin/default, but pushRef as origin/branch, as shown in Figure 9.

Working with triangular forks requires a bit more customization than triangular branches because we are dealing with multiple remotes. […]

you are viewing a single comment's thread
view the rest of the comments

[-] [email protected] 3 points 1 month ago

How is that different from sending a PR?

[-] [email protected] 5 points 1 month ago

For a single PR it's pretty much the same, but if you have multiple back and forth, you'd have to set up multiple remotes and switch between them. Now you don't. If I understand it correctly, you can now just "git pull" from repo1 and "git push" to repo2

[-] [email protected] 2 points 1 month ago

Not oc, but thank you for explaining

this post was submitted on 25 Apr 2025

14 points (85.0% liked)

Git

3456 readers

4 users here now

Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.

Resources

Rules

Follow programming.dev rules
Be excellent to each other, no hostility towards users for any reason
No spam of tools/companies/advertisements. It’s OK to post your own stuff part of the time, but the primary use of the community should not be self-promotion.

Git Logo by Jason Long is licensed under the Creative Commons Attribution 3.0 Unported License.

founded 2 years ago

MODERATORS

[email protected]