-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1 from Microkubes/add-contribution-guide
Add contribution guide
- Loading branch information
Showing
2 changed files
with
30 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
## Contributing | ||
|
||
If you want to contribute to a project and make it better, your help is very welcome. Contributing is also a great way to learn more about social coding on Github, new technologies and their ecosystems and how to make constructive, helpful bug reports, feature requests and the noblest of all contributions: a good, clean pull request. | ||
|
||
### How to make a clean pull request | ||
|
||
Look for a project's contribution instructions. If there are any, follow them. | ||
|
||
- Create a personal fork of the project on Github. | ||
- Clone the fork on your local machine. Your remote repo on Github is called `origin`. | ||
- Add the original repository as a remote called `upstream`. | ||
- If you created your fork a while ago be sure to pull upstream changes into your local repository. | ||
- Create a new branch to work on! | ||
- Implement/fix your feature, comment your code. | ||
- Follow the code style of the project, including indentation. | ||
- If the project has tests run them! | ||
- Write or adapt tests as needed. | ||
- Add or change the documentation as needed. | ||
- Squash your commits into a single commit with git's [interactive rebase](https://help.github.com/articles/interactive-rebase). Create a new branch if necessary. | ||
- Push your branch to your fork on Github, the remote `origin`. | ||
- From your fork open a pull request in the correct branch. | ||
- ... | ||
- Once the pull request is approved and merged you can pull the changes from `upstream` to your local repo and delete | ||
your extra branch(es). | ||
|
||
And last but not least: Always write your commit messages in the present tense. Your commit message should describe what the commit, when applied, does to the code – not what you did to the code. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters