Skip to content

Commit

Permalink
add note to readme about current status & relation to --update-refs
Browse files Browse the repository at this point in the history
  • Loading branch information
kiprasmel committed Feb 27, 2024

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
1 parent ac73e33 commit cc95c6b
Showing 1 changed file with 8 additions and 0 deletions.
8 changes: 8 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
@@ -19,6 +19,14 @@ a branch is just a reference to some commit (literally, it's a single-line file

from those partial branches, you can create pull requests. with this workflow, you get to comfortably iterate in a single branch; your teammates get the benefits of reviewing smaller PRs (when they're ready). win win. that's it.

## a note about git rebase --update-refs

git-stacked-rebase got started 6 months before git rebase learned its own `--update-refs`.
for the purposes of simply updating branches that are part of your stack,
git's rebase with --update-refs works just fine.
git-stacked-rebase still has unique features (and novel ideas yet to be implemented),
ut hasn't been maintained for a little while now. this may change when i get more capacity to work on it.

---

`git-stacked-rebase` is not specific to any host like github or gitlab. it's "specific" to `git` itself.

0 comments on commit cc95c6b

Please sign in to comment.