You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+5-5
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ See this handy, if ugly, [cheat sheet](http://danielkummer.github.io/git-flow-ch
16
16
2. clone your fork to your local development machine
17
17
3. Set this repo as the `upstream` repo `git remote add upstream <insert the upstream url>`
18
18
4. Disallow direct pushing to upstream `git remote set-url --push upstream no_push`
19
-
5. create a local `master` branch `git checkout -b master` and test it via `git pull upstream master`
19
+
5. create a local `main` branch `git checkout -b main` and test it via `git pull upstream main`
20
20
6. ensure you have installed the [`git-flow` command line helpers](https://github.com/nvie/gitflow) and [`git-flow-completion` utils](https://github.com/bobthecow/git-flow-completion) then run `git flow init -d`.
It's basically the same process but use the word `hotfix` or `support` instead of `feature`. `git flow` knows what to do. Just keep in mind that any changes are going to happen to your fork, and not the upstream repo. If you need to merge a `hotfix` into upstream master you may only do it va a reviewed pull request.
49
+
It's basically the same process but use the word `hotfix` or `support` instead of `feature`. `git flow` knows what to do. Just keep in mind that any changes are going to happen to your fork, and not the upstream repo. If you need to merge a `hotfix` into upstream main you may only do it va a reviewed pull request.
2. commit any changes to version info in `package.json` then `git flow release publish {tag.number}`
55
-
3.`git flow release finish {tag.number}` merges the release into `master` of your fork, tags it, merges that back into `develop` on your fork and removes the release branch.
56
-
4. Now go back to GitHub and raise a Pull Request to merge the upstream master from your fork's `master` branch. When that goes through you are done.
57
-
5. In your command-line go back and clean up any outstanding branches and `git pull upstream` your local `master` and `develop` branches to ensure everything on your local machine is up to date with everyone's changes.
55
+
3.`git flow release finish {tag.number}` merges the release into `main` of your fork, tags it, merges that back into `develop` on your fork and removes the release branch.
56
+
4. Now go back to GitHub and raise a Pull Request to merge the upstream main from your fork's `main` branch. When that goes through you are done.
57
+
5. In your command-line go back and clean up any outstanding branches and `git pull upstream` your local `main` and `develop` branches to ensure everything on your local machine is up to date with everyone's changes.
58
58
59
59
Note you will **never** push changes directly to the upstream project, _only to your own fork_.
|`develop`|[](https://circleci.com/gh/davesag/amqp-simple-pub-sub/tree/develop)|[](https://codecov.io/gh/davesag/amqp-simple-pub-sub)|[](https://snyk.io/test/github/davesag/amqp-simple-pub-sub/develop)| Work in progress |
0 commit comments