Copyleft/guide
6
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Note merge request should usually target next.

Browse source 
Some targets to master are acceptable, though.
This commit is contained in:
Bradley M. Kuhn 2014-12-20 17:21:31 -05:00
parent e1373883c9
commit 57e8fa1cb2
1 changed files with 11 additions and 2 deletions

13
CONTRIBUTING.md
View file

@ -74,6 +74,15 @@ development on the project happens on the
(which is (which is
[auto-published on the copyleft.org/guide-next URL](https://copyleft.org/guide-next/)). [auto-published on the copyleft.org/guide-next URL](https://copyleft.org/guide-next/)).
Here is a suggested workflow for submitting patches — first doing so Here is a suggested workflow for submitting patches — first doing so
*with* the Gitorious infrastructure and second *avoiding* the Gitorious *with* the Gitorious infrastructure, second *avoiding* the Gitorious
infrastructure. infrastructure but still using Git, and third avoiding Git altogether.
Merge requests and/or patches against
['next' branch](https://gitorious.org/copyleft-org/tutorial/source/next:) are
typically much preferred, and the workflow explanations below assume that.
However, merge requests and/or patches against
['master' branch](https://gitorious.org/copyleft-org/tutorial/source/master:)
are not necessarily rejected. In fact, if your change is a fix for typo,
spelling, grammar, formatting or anything urgent, submitting a patch against
'master' may make more sense.