3 ms·
Does this do anything beyond helping you and your team keep track of which branches your feature branch is based off of, and which order they should be merged i
by yosito 5y ago
Does this do anything beyond helping you and your team keep track of which branches your feature branch is based off of, and which order they should be merged in? I think you can already do this in git / GitHub. I usually do it by starting a PR with "based on #n which should be merged first". You can stack any number of PRs that way. You can even set the PR target to the base branch to narrow down your diff for review, and change the target to your main branch any time you want. What does Graphite add to this workflow?
- fosterfriends 5y agoGreat question! It does lots of things. The CLI (https://github.com/screenplaydev/graphite-cli https://github.com/screenplaydev/graphite-cli) lets you: - Recursively rebase changes to keep your branches correctly stacked - Allow you to shift half of a stack onto a different branch - Open up PRs/push changes for all the branches in a stack - Offer to delete merged branches from local, rebases the remaining branches, and adjust github pr merge bases. The web dashboard lets you: - See an inbox of PRs spanning any number of repos, based on which ones need action - Navigate between PRs in a stack - Modify Prs, review, all of which is synced to Github - Shortcuts, client side caching for fast loading, Phabricator style interface, macros, landing a stack of PRs together, and much more :) Give the tool a try, we'd love to hear your feedback in the community Slack! https://join.slack.com/t/graphite-community/shared_invite/zt-v828g9dz-TIRvlutxTCqgZmxnsO9Knw https://join.slack.com/t/graphite-community/shared_invite/zt...