-
Notifications
You must be signed in to change notification settings - Fork 3
Contributing
Franz Josef Kaiser edited this page Aug 23, 2015
·
1 revision
We happily accept Pull Requests and reward them with contributor access!
Before adding a new issue or filing a Pull Request, please take a look at the existing issues and open _Pull Requests.
Please always open a new issue and fork the plugin. Before starting
to work on code changes, please make sure that you check out a new branch
starting with issue-
:
git checkout -b issue-9
Add as many commits as possible for your changes. When you write a commit message, please…
- use
feat
,refactor
,style
,fix
ordocs
for the start of your msg - set the topic into braces
- write a meaningful message (can be multiple lines long)
- add a hash
#
and the issue number to the message, so GitHub can refer it
Example:
git commit -m "fix(loader) Fix icon not appearing, see #9"
When you push to your remote repo, please push the issue-
branch to
remote when sending your Pull Request. This allows us to check your
branch locally and in isolation before merging it back into dev
and
finally into master
and tagging it for a new release.
Thanks a bunch for contributing!