top | item 46159639 (no title) jbjbjbjb | 2 months ago I think ‘git rebase —-update-refs’ is the better way to go for this scenario discuss order hn newest unknown|2 months ago [deleted] lelandfe|2 months ago Sweet, looks like this is pretty new (2022).Running a git command on one branch and multiple branches being affected is really unusual for me! This really does look like it is designed for just this problem, though. Simple overview: https://blog.hot-coffee.dev/en/blog/git_update_refs/ YmiYugy|2 months ago It breaks if you amend the top commit instead of adding a new one. enbugger|2 months ago Is there any good guide on how to solve the issue which OP solves? jbjbjbjb|2 months ago I was reading this the other day when I came across this feature because I’m stacking PRs recently which I don’t usually dohttps://andrewlock.net/working-with-stacked-branches-in-git-...Another commenter posted this link which was a bit more succincthttps://blog.hot-coffee.dev/en/blog/git_update_refs/There isn’t much to it though, you just go to the branch and run git rebase with the update refs flag. sirsuki|2 months ago You don’t really need docs as --update-refs does what the OP does automatically instead of manually like the OP does. load replies (1)
lelandfe|2 months ago Sweet, looks like this is pretty new (2022).Running a git command on one branch and multiple branches being affected is really unusual for me! This really does look like it is designed for just this problem, though. Simple overview: https://blog.hot-coffee.dev/en/blog/git_update_refs/
enbugger|2 months ago Is there any good guide on how to solve the issue which OP solves? jbjbjbjb|2 months ago I was reading this the other day when I came across this feature because I’m stacking PRs recently which I don’t usually dohttps://andrewlock.net/working-with-stacked-branches-in-git-...Another commenter posted this link which was a bit more succincthttps://blog.hot-coffee.dev/en/blog/git_update_refs/There isn’t much to it though, you just go to the branch and run git rebase with the update refs flag. sirsuki|2 months ago You don’t really need docs as --update-refs does what the OP does automatically instead of manually like the OP does. load replies (1)
jbjbjbjb|2 months ago I was reading this the other day when I came across this feature because I’m stacking PRs recently which I don’t usually dohttps://andrewlock.net/working-with-stacked-branches-in-git-...Another commenter posted this link which was a bit more succincthttps://blog.hot-coffee.dev/en/blog/git_update_refs/There isn’t much to it though, you just go to the branch and run git rebase with the update refs flag.
sirsuki|2 months ago You don’t really need docs as --update-refs does what the OP does automatically instead of manually like the OP does. load replies (1)
unknown|2 months ago
[deleted]
lelandfe|2 months ago
Running a git command on one branch and multiple branches being affected is really unusual for me! This really does look like it is designed for just this problem, though. Simple overview: https://blog.hot-coffee.dev/en/blog/git_update_refs/
YmiYugy|2 months ago
enbugger|2 months ago
jbjbjbjb|2 months ago
https://andrewlock.net/working-with-stacked-branches-in-git-...
Another commenter posted this link which was a bit more succinct
https://blog.hot-coffee.dev/en/blog/git_update_refs/
There isn’t much to it though, you just go to the branch and run git rebase with the update refs flag.
sirsuki|2 months ago