Skip to content

[DOC] contribution guide: clarify commit prefixes + work-file annotations#5678

Open
dnplkndll wants to merge 2 commits into
OCA:documentationfrom
ledoent:doc/contribution-guide-clarity
Open

[DOC] contribution guide: clarify commit prefixes + work-file annotations#5678
dnplkndll wants to merge 2 commits into
OCA:documentationfrom
ledoent:doc/contribution-guide-clarity

Conversation

@dnplkndll
Copy link
Copy Markdown

Two small clarifications to the contribution guide, plus a brand-consistency pass.

090_contribute.rst

  • [MIG] <module> is the standard prefix for a module's whole migration (analysis annotations and/or pre/post scripts). The previous text implied [ADD]/[OU-ADD]; recent 19.0 history is overwhelmingly [MIG] (used with and without scripts), with [OU-ADD]/[OU-FIX]/[OU-IMP] reserved for framework / cross-cutting changes.
  • Work-file annotations go inline, one per analysis line; empty sections (a ---<Type> in module 'X'--- header with no lines under it) get no marker — left blank.

Brand-name capitalizationOpenupgradeOpenUpgrade, odooOdoo across four narrative files.

Source-only: docs/ is regenerated by the documentation-commit workflow on push.

dnplkndll added 2 commits May 30, 2026 14:15
- [MIG] <module> is the standard prefix for a module's whole migration
  (annotations and/or scripts); [OU-ADD]/[OU-FIX]/[OU-IMP] are for
  framework/cross-cutting changes. Fixes the stale [ADD] example.
- Work-file annotations go inline per analysis line; empty sections
  (header with no lines) get no marker.
@dnplkndll dnplkndll force-pushed the doc/contribution-guide-clarity branch from 144f7e4 to ef96e12 Compare May 30, 2026 18:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant