avCLI and MergeQueue to managed stacked PRs
Add the /books/list route to the backendand PR2 is
Show the books list in the frontend, we can stack PR2 on top of PR1. This means that you don’t have to wait for PR1 to be reviewed and merged before you can start PR2 (and they can even be reviewed by separate people!).
avCLI) and during the merge process (using MergeQueue).
avtool. Make sure to add a GitHub access token to your settings file and run
av initin the repository where you'll be working with stacked PRs.
av stack branchcommand. It requires one argument which is the name of the branch to create. The
av stack branchcommand creates a "normal" Git branch (though we're branching from
mainsince we want to build off of our previous work) and also sets some internal data to be able to recognize that
bookstore-frontendis dependent on
av pr createcommand again.
mainto ensure that GitHub shows the diff between
bookstore-backend(otherwise, it would show all the changes from
bookstore-backendin the PR for
bookstore-frontendwhich would make code review much harder).
/aviator stack mergecommand on the GitHub PR (as a slash command comment).
av stack sync.
av stack synccommand is used to make sure every branch is up-to-date with its stack parent.
av stack syncto propagate the changes to all children branches.