this post was submitted on 25 Apr 2025
14 points (85.0% liked)

Git

3222 readers
15 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

  1. Follow programming.dev rules
  2. Be excellent to each other, no hostility towards users for any reason
  3. 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
Ategon
canpolat
jnovinger
14
How the GitHub CLI can now enable triangular workflows (github.blog)
submitted 1 day ago* (last edited 1 day ago) by Kissaki to c/git
6 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
[–] Colloidal 3 points 15 hours ago (1 children)

How is that different from sending a PR?

[–] [email protected] 4 points 14 hours ago (1 children)

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 10 hours ago

Not oc, but thank you for explaining