go/lazygit
1
0
Fork 0
mirror of https://github.com/jesseduffield/lazygit.git synced 2025-02-13 13:59:06 +02:00
Code Issues Releases Activity

Update Stacked_Branches.md

Browse Source 
Fix a typo.
This commit is contained in:
Alan Potter 2023-10-24 05:32:29 -04:00 committed by GitHub
parent 8193731a82
commit 4d18b62c54
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/Stacked_Branches.md
View File

@ -7,7 +7,7 @@ refactorings, one for backend changes, and one for frontend changes. Those
branches would then all be stacked onto each other. branches would then all be stacked onto each other.
Git has support for rebasing such a stack as a whole; you can enable it by Git has support for rebasing such a stack as a whole; you can enable it by
setting the git config `rebase.updateRfs` to true. If you then rebase the setting the git config `rebase.updateRefs` to true. If you then rebase the
topmost branch of the stack, the other ones in the stack will follow. This topmost branch of the stack, the other ones in the stack will follow. This
includes interactive rebases, so for example amending a commit in the first includes interactive rebases, so for example amending a commit in the first
branch of the stack will "just work" in the sense that it keeps the other branch of the stack will "just work" in the sense that it keeps the other