mirror-games/glest-source
1
0
Fork 0
mirror of https://github.com/glest/glest-source.git synced 2025-09-25 15:09:03 +02:00
Code Issues Projects Releases Wiki Activity

CONTRIBUTING.md: add note about [skip ci]

Browse Source
This commit is contained in:
andy5995
2018-01-24 22:03:46 -06:00
parent 534d2ae466
commit 9e704ce28a
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
CONTRIBUTING.md
View File

@@ -69,7 +69,13 @@ repositories.
4. Make your changes. If you're unsure of some details while you're making edits, you can 4. Make your changes. If you're unsure of some details while you're making edits, you can
discuss them on the ticket. discuss them on the ticket.
5. Add yourself to the [AUTHORS.md](https://github.com/ZetaGlest/zetaglest-source/blob/develop/AUTHORS.md) file 5. Add yourself to the [AUTHORS.md](https://github.com/ZetaGlest/zetaglest-source/blob/develop/AUTHORS.md) file
6. Commit your changes. [git-cola](https://git-cola.github.io/) is a nice GUI front-end for adding files and entering commit messages (git-cola is probably available from your OS repository). 6. Commit your changes. [git-cola](https://git-cola.github.io/) is a nice GUI front-end for adding files and entering commit messages (git-cola is probably available from your OS repository).
* If you're updating only documention (or other files that don't
affect a build) add [skip ci] to the commit message (code integration
will be skipped)
7. Push the working branch (e.g. issue_32) to your remote fork and make your 7. Push the working branch (e.g. issue_32) to your remote fork and make your
[pull request](https://help.github.com/articles/creating-a-pull-request-from-a-fork/) [pull request](https://help.github.com/articles/creating-a-pull-request-from-a-fork/)
* Do not merge it with the master branch on your fork. That would result in multiple, or * Do not merge it with the master branch on your fork. That would result in multiple, or