No branches? No problem.
Get a taste for the Git Patch Stack workflow, the tooling, and what it might feel like to join the revolution of stacking patches rather than making and managing branches.
Helping you make smaller pull requests
Build small, logical, buildable, testable, releasable, patches while supporting pre-commit peer review via the tools everyone is used to (GitHub, BitBucket, GitLab, etc).
Listgps list (ls)
List out all the patches in your current stack along with their associated states.
Create Patchgps create-patch (c)
Create a logical, buildable, testable patch on top of your current stack of patches.
Refine Patchesgps rebase
Refine patches iteratively as we prepare our patches for review.
Pull git history from upstream and rebase your stack on top of the latest.
Request Reviewgps request-review (rr)
Request review of a specific patch in your patch stack.
Integrategps integrate (int)
Integrate your reviewed and approved patch into upstream.
Need some help? Or maybe you just want some deeper insights into why Git Patch Stack is the way it is and how best to use it. Well, check out some of these helpful resources.
Journey to Small Pull Requests
This article provides great background to our thought process and the exploration that we followed to find a workflow to help make and manage smaller pull requests. This also happens to be the back story for Git Patch Stack as it is the tool we invented to help facilitate this workflow.
We're here to help
Have questions, suggestions, etc. Don't hesitate to let us know. Learning from our users and understanding all of their use cases is the only way we can improve Git Patch Stack beyond our own usecases.