From cc95c6b1ce5df885cf9ed49cc3a24f9251e7f235 Mon Sep 17 00:00:00 2001 From: Kipras Melnikovas Date: Tue, 27 Feb 2024 21:53:49 +0200 Subject: [PATCH] add note to readme about current status & relation to --update-refs --- README.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/README.md b/README.md index 22822a0a..feab3343 100644 --- a/README.md +++ b/README.md @@ -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.