diff options
| author | dannmat <mattwardiom> | 2019-10-15 22:38:38 +0100 |
|---|---|---|
| committer | dannmat <mattwardiom> | 2019-10-20 11:47:42 +0100 |
| commit | f09ba060cacd42e4cb9a242c1d731deb1f6623c6 (patch) | |
| tree | e7f5f1dd640c7b4483fd5aa63face2f4f96765db /CONTRIBUTING.md | |
| parent | eb292af309aa57f3d7998b01307dd4cb91702908 (diff) | |
| download | bitcoin-f09ba060cacd42e4cb9a242c1d731deb1f6623c6.tar.xz | |
doc: Added instructions for how to add an upsteam to forked repo
As a first time git developer, I struggled to understand whether to create a new fork for each pull request or not.
After asking the IRC chat, I have added this to the documentation to further help new developers using git.
Co-Authored-By: Michael <fanquake@gmail.com>
Diffstat (limited to 'CONTRIBUTING.md')
| -rw-r--r-- | CONTRIBUTING.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 1f4a2c081e..ecb5704a8f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -46,7 +46,7 @@ facilitates social contribution, easy testing and peer review. To contribute a patch, the workflow is as follows: - 1. Fork repository + 1. Fork repository ([only the first time](https://help.github.com/en/articles/fork-a-repo)). 1. Create topic branch 1. Commit patches |