ansible/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
Code Releases Activity

xpace

Browse source
This commit is contained in:
Brian Coca 2016-09-19 14:00:51 -04:00
parent 322880f898
commit 1095d7e615
1 changed files with 2 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docsite/rst/committer_guidelines.rst
View file

@ -42,6 +42,7 @@ General Rules
Individuals with direct commit access to ansible/ansible (+core, + extras) are entrusted with powers that allow them to do a broad variety of things--probably more than we can write down. Rather than rules, treat these as general *guidelines*, individuals with this power are expected to use their best judgement. Individuals with direct commit access to ansible/ansible (+core, + extras) are entrusted with powers that allow them to do a broad variety of things--probably more than we can write down. Rather than rules, treat these as general *guidelines*, individuals with this power are expected to use their best judgement.
* Don’t * Don’t
- Commit directly. - Commit directly.
- Merge your own PRs. Someone else should have a chance to review and approve the PR merge. If you are a Core Committer, you have a small amount of leeway here for very minor changes. - Merge your own PRs. Someone else should have a chance to review and approve the PR merge. If you are a Core Committer, you have a small amount of leeway here for very minor changes.
- Forget about alternate environments. Consider the alternatives--yes, people have bad environments, but they are the ones who need us the most. - Forget about alternate environments. Consider the alternatives--yes, people have bad environments, but they are the ones who need us the most.
@ -51,6 +52,7 @@ Individuals with direct commit access to ansible/ansible (+core, + extras) are e
- Forget to keep it simple. Complexity breeds all kinds of problems. - Forget to keep it simple. Complexity breeds all kinds of problems.
* Do * Do
- Squash, avoid merges whenever possible, use github's squash commits or cherry pick if needed (bisect thanks you). - Squash, avoid merges whenever possible, use github's squash commits or cherry pick if needed (bisect thanks you).
- Be active. Committers who have no activity on the project (through merges, triage, commits, etc.) will have their permissions suspended. - Be active. Committers who have no activity on the project (through merges, triage, commits, etc.) will have their permissions suspended.
- Consider backwards compatibility (goes back to "don’t break existing playbooks"). - Consider backwards compatibility (goes back to "don’t break existing playbooks").