generated from the-liberated-edge/wikijs
i-1 Introduces an Ansible playbook for linux-container with SSH access #2
11
README.md
11
README.md
@ -103,18 +103,17 @@ rule in our source control system.
|
||||
commit that has been merged in the `main` branch.
|
||||
3. Every git pull request has been linked to exactly one project issue. The
|
||||
issue number prefixes the pull request title, e.g. `i-1 <pull request title>`.
|
||||
4. The change has been thoroughly reviewed and all discovered issues have
|
||||
been resolved. Merging without a code review approval is only acceptable
|
||||
when reviewers are not available.
|
||||
5. The change has been tested by Ansible Molecule scenarios. Our team adopted
|
||||
4. The change has been tested by Ansible Molecule scenarios. Our team adopted
|
||||
an approach resembling Test Driven Development for the sake of automated
|
||||
regression testing.
|
||||
6. All automated tests have been passing successfully consistently. We have
|
||||
5. All automated tests have been passing successfully consistently. We have
|
||||
zero tolerance on test flakiness.
|
||||
7. Source code has been linted with `yamllint` and `ansible-lint`. Any errors
|
||||
6. Source code has been linted with `yamllint` and `ansible-lint`. Any errors
|
||||
have been fixed.
|
||||
8. All YAML documents have been formated with `yamlfix`.
|
||||
9. User facing changes have been documented appropriately.
|
||||
7. All YAML documents have been formated with `yamlfix`.
|
||||
8. User facing changes have been documented appropriately.
|
||||
|
||||
## Development environment setup
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user