| ... | @@ -9,11 +9,11 @@ Development process happens on the development branches (named `11.0-<branch nam |
... | @@ -9,11 +9,11 @@ Development process happens on the development branches (named `11.0-<branch nam |
|
|
Any code changes should pass the following stages to be merged into the main branch:
|
|
Any code changes should pass the following stages to be merged into the main branch:
|
|
|
|
|
|
|
|
1. Automatic static code analysis
|
|
1. Automatic static code analysis
|
|
|
With the following code analyzers:
|
|
With the following code analyzers:
|
|
|
- [bandit](https://github.com/PyCQA/bandit)
|
|
- [bandit](https://github.com/PyCQA/bandit)
|
|
|
- [palynt](https://github.com/OCA/pylint-odoo), [flake8](https://github.com/PyCQA/flake8)
|
|
- [palynt](https://github.com/OCA/pylint-odoo), [flake8](https://github.com/PyCQA/flake8)
|
|
|
- [stylelint](https://github.com/stylelint/stylelint)
|
|
- [stylelint](https://github.com/stylelint/stylelint)
|
|
|
- check-versions (ensure that changes to main branches will change the version of addons)
|
|
- check-versions (ensure that changes to main branches will change the version of addons)
|
|
|
2. Automatic tests
|
|
2. Automatic tests
|
|
|
- on a clean database
|
|
- on a clean database
|
|
|
- tests with the changes made (migration tests)
|
|
- tests with the changes made (migration tests)
|
| ... | | ... | |
