r/p5.js-web-editor
1
0
Fork 0
Code Issues 1 Pull requests Releases 1 Wiki Activity

[WIP] Add detailed git workflow (#603)

Browse source 
* add git workflow

* fix

* update contributing.md

* add github guides/remove git parts

* add github guides/remove git parts

* update
This commit is contained in:
Mr.tang 2018-03-16 23:44:55 +08:00 committed by Cassie Tarakajian
parent 432393c63b
commit 3fba506589
1 changed files with 14 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
contributing.md
View file

@ -62,9 +62,22 @@ If you'd like to work on a bug, please comment on it to let the maintainers know
If someone else has already commented and taken up that bug, please refrain from working on it and submitting If someone else has already commented and taken up that bug, please refrain from working on it and submitting
a PR without asking the maintainers as it leads to unnecessary duplication of effort. a PR without asking the maintainers as it leads to unnecessary duplication of effort.
### Contribution guides
* [https://guides.github.com/activities/hello-world/](https://guides.github.com/activities/hello-world/)
* [https://guides.github.com/activities/forking/](https://guides.github.com/activities/forking/)
# Creating a pull request # Creating a pull request
When you create a [pull request](https://help.github.com/articles/creating-a-pull-request/) for a new fix or feature, be sure to mention the issue number for what you're working on. The best way to do it is to mention the issue like this at the top of your description: Set up a new remote that points to the original project so that you can update your local repository once any changes have made to remote.
$ git remote add upstream https://github.com/processing/p5.js-web-editor
and also before you submit a [pull request](https://help.github.com/articles/creating-a-pull-request/), please remember to fetch the changes using:
$ git fetch upstream
When you create a pull request for a new fix or feature, be sure to mention the issue number for what you're working on. The best way to do it is to mention the issue like this at the top of your description:
Fixes #333 Fixes #333