add paragraph to cdist-hacker that states manpages always need to build on merge request
Signed-off-by: Nico Schottelius <nico@kr.ethz.ch>
This commit is contained in:
parent
60fab053f2
commit
1d2ec72396
1 changed files with 2 additions and 3 deletions
|
@ -46,9 +46,8 @@ work nor kill the authors brain:
|
||||||
private branch!
|
private branch!
|
||||||
- Code to be included should be branched of the upstream "master" branch
|
- Code to be included should be branched of the upstream "master" branch
|
||||||
- Exception: Bugfixes to a version branch
|
- Exception: Bugfixes to a version branch
|
||||||
- Code submissions should be in your master branch
|
- On a merge request, always name the branch I should pull from
|
||||||
- Other branches are fine as well, but you need to tell me which branch
|
- Always ensure **all** manpages build: ./build.sh man
|
||||||
your work is in!
|
|
||||||
- If you developed more than **one** feature, consider submitting them in
|
- If you developed more than **one** feature, consider submitting them in
|
||||||
seperate branches. This way one feature can already be included, even if
|
seperate branches. This way one feature can already be included, even if
|
||||||
the other needs to be improved.
|
the other needs to be improved.
|
||||||
|
|
Loading…
Reference in a new issue