phantom/bitcoin
1
0
Fork 0
mirror of https://github.com/bitcoin/bitcoin.git synced 2025-02-02 14:37:42 -03:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

doc: Explain squashing with merge commits

Browse source
This commit is contained in:
MacroFake 2022-05-18 10:27:49 +02:00
parent 44037a2912
commit fa2d226ac9
No known key found for this signature in database
GPG key ID: CE2B75697E69A548
1 changed files with 6 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
CONTRIBUTING.md
View file

@ -216,9 +216,9 @@ Please update the resulting commit message, if needed. It should read as a
coherent message. In most cases, this means not just listing the interim coherent message. In most cases, this means not just listing the interim
commits. commits.
If you have problems with squashing or other git workflows, you can enable If your change contains a merge commit, the above workflow may not work and you
"Allow edits from maintainers" in the right-hand sidebar of the GitHub web will need to remove the merge commit first. See the next section for details on
interface and ask for help in the pull request. how to rebase.
Please refrain from creating several pull requests for the same change. Please refrain from creating several pull requests for the same change.
Use the pull request that is already open (or was created earlier) to amend Use the pull request that is already open (or was created earlier) to amend
@ -231,7 +231,9 @@ pull request to pull request.
### Rebasing Changes ### Rebasing Changes
When a pull request conflicts with the target branch, you may be asked to rebase it on top of the current target branch. When a pull request conflicts with the target branch, you may be asked to rebase it on top of the current target branch.
The `git rebase` command will take care of rebuilding your commits on top of the new base.
git fetch https://github.com/bitcoin/bitcoin # Fetch the latest upstream commit
git rebase FETCH_HEAD # Rebuild commits on top of the new base
This project aims to have a clean git history, where code changes are only made in non-merge commits. This simplifies This project aims to have a clean git history, where code changes are only made in non-merge commits. This simplifies
auditability because merge commits can be assumed to not contain arbitrary code changes. Merge commits should be signed, auditability because merge commits can be assumed to not contain arbitrary code changes. Merge commits should be signed,