arc for github

[epage]

When I'm working on multiple PRs, I also sometimes want them on the same branch so I can test against the whole. The arc workflow worked well for this, with the main problem being forced ordering for merges. Granted, I still like multi-commit PRs which phab frowned upon.

Prior art:

• ghstack
  • Manages custom branches upstream, with ghstack land actually pulling it into the real master (e.g.)
  • Uses a tree hash as an ID in some places
• gh-stack
• how to implement stacked diffs on GH
  • Uses the commit subject as the branch name
  • Squashes in master but keeps individual commits in the branch
• another how to
  • See gh-stack
  • This seems to use branch names to tag specific points with the remote having mirror branches
• Stacked Git
• git-ps
  • and blog post
• git-branchless

What if we made a custom rebase, git rewrite

• Columns: Action, Branch, SHA, Summary
  • Branch is ^ when just a commit on the branch
• After performing rebase, git reset --hard the branch names (or delete branches) and cherry-pick the old commits back on top
  • Or use --onto (probably easier for fixup, see below, because useer might have deleted commits, etc)
• Check all branches not mentioned in rebase to see if they share a merge-base, and rebase them
  • A git fixup command to check tree hashes and rebase branches accordingly in case the user does a git pull --rebase or something similar
• git publish will sync the state with remote branches and create PRs if needed

[epage]

Names

• git-rewrite
• git-stack
• git-brack ("branch stack")

Store target branch in the footer

Names

• git-pr

By default shows pr status

Can --update

• Skip branches with WIP
• either first commit, everything reachable from HEAD, and/or all branches at mismatch with remote

Inserts/updates a "depends on" footer in each PR