[IMP] CODEOWNERS: add new codeowner for technical files

# If you feel that it might help a future reader to understand your commit
# motivations, take some time to explain WHY you made these changes in a few
# sentences. The WHAT is usually easily understood by reading the diff.
#
# Short description tip: structure your commit message as if it was completing
# this sentence: "If merged, this commit will ...". For instance, the following
# commit message is correct: "[IMP] sales: compress images to save space".
#
# Tag meanings:
#
# [ADD] = New content
# [IMP] = Improvement
# [FIX] = Content or RST fix
# [REM] = Removal
# [REF] = Refactoring (restructuring)
# [MOV] = Move/rename
#
This commit is contained in:
Antoine Vandevenne (anv) 2021-05-05 11:09:31 +02:00
parent c820a96e2d
commit c3eddb6286

12
.github/CODEOWNERS vendored
View File

@ -1,3 +1,11 @@
# All changes to technical files (build environment and Sphinx extensions) have to be approved
/extensions/ @odoo/doc-review
.gitignore @odoo/doc-review
commit_template.txt @odoo/doc-review
conf.py @odoo/doc-review
Makefile @odoo/doc-review
requirements.txt @odoo/doc-review
# All changes to legal material have to be approved
/legal/ @odoo/legal
/legal.rst @odoo/legal
/content/legal/ @odoo/legal
/content/legal.rst @odoo/legal