Ansible-lint and yamllint #32
|
@ -3,15 +3,15 @@
|
||||||
Contributions are welcome, as long as they respect our current workflow:
|
Contributions are welcome, as long as they respect our current workflow:
|
||||||
|
|
||||||
1. The master branch is only for releases. Once properly tested,
|
1. The master branch is only for releases. Once properly tested,
|
||||||
the dev branch can be merged, the release tagged and a tar archive
|
the dev branch can be merged, the release tagged and a tar archive
|
||||||
created.
|
created.
|
||||||
|
|
||||||
2. The dev branch should never be commited to directly, unless
|
2. The dev branch should never be commited to directly, unless
|
||||||
you're updating the CHANGELOG file.
|
you're updating the CHANGELOG file.
|
||||||
|
|
||||||
3. Use feature branches for anything else, once they've passed all
|
3. Use feature branches for anything else, once they've passed all
|
||||||
CI test, lints and have been reviewed by other contributors through a
|
CI test, lints and have been reviewed by other contributors through a
|
||||||
pull request, they may be merged into the dev branch.
|
pull request, they may be merged into the dev branch.
|
||||||
|
|
||||||
|
|
||||||
Open issues liberally, but please review closed and opened issues
|
Open issues liberally, but please review closed and opened issues
|
||||||
|
|
Loading…
Reference in a new issue