mirror of
https://github.com/bitcoin/bitcoin.git
synced 2025-01-25 18:53:23 -03:00
Merge #21263: doc: Clarify that squashing should happen before review
fa1f3a26a7
doc: Clarify that squashing should happen before review (MarcoFalke) Pull request description: Unlike other repos, in our repo code review happens before merge, ideally. Thus, rebases, solving merge conflicts and squashing should happen before review, which again happens before merge. ACKs for top commit: theStack: ACKfa1f3a26a7
fanquake: ACKfa1f3a26a7
Tree-SHA512: e9222191a6e9cf9867bd1f29982526dd7b746b70dd2cc94f485256ec98ff2d3941c9b40728935e151d13795239334e334b71ad41044909cb2849f57776811a94
This commit is contained in:
commit
1e7dd584a5
1 changed files with 1 additions and 1 deletions
|
@ -197,7 +197,7 @@ Note: Code review is a burdensome but important part of the development process,
|
|||
|
||||
If your pull request contains fixup commits (commits that change the same line of code repeatedly) or too fine-grained
|
||||
commits, you may be asked to [squash](https://git-scm.com/docs/git-rebase#_interactive_mode) your commits
|
||||
before it will be merged. The basic squashing workflow is shown below.
|
||||
before it will be reviewed. The basic squashing workflow is shown below.
|
||||
|
||||
git checkout your_branch_name
|
||||
git rebase -i HEAD~n
|
||||
|
|
Loading…
Add table
Reference in a new issue