Learn more about triangular workflows, how they work, and how to configure them for your Git workflows. See how you can leverage them on the GitHub CLI.

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. […]

  • chonkyninja@lemmy.worldEnglish
    31·
    1 day ago

    Yeah, because fucking Reviewing merge requests, my code is AI generated, it can’t possibly have any errors. /s