Skip to content

[DOC] 090_contribute: per-line inline annotation markers#41

Draft
dnplkndll wants to merge 2 commits into
documentationfrom
doc/annotation-grouping
Draft

[DOC] 090_contribute: per-line inline annotation markers#41
dnplkndll wants to merge 2 commits into
documentationfrom
doc/annotation-grouping

Conversation

@dnplkndll
Copy link
Copy Markdown

What

Updates the annotation Note in `docsource/090_contribute.rst` to describe the inline-per-line marker convention that reviewers consistently ask for.

Current text allows grouping:

You can reorder lines and group them together for including all of them in a "logical" block for putting only one comment.

Proposed text describes the inline-per-line convention:

Place each marker inline, on its own line, immediately following the specific analysis line it annotates. Don't consolidate multiple adjacent analysis lines under a single grouped comment …

Plus:

  • A sentence about empty section headers still getting a marker
  • A short `code-block:: text` example showing the expected shape

Why

The current "logical block consolidated comments" guidance contradicts what reviewers ask for on recent 19.0 PRs. Several recent PRs have been sent back with requests to expand consolidated blocks into inline per-line markers. Aligning the doc with the practice reduces re-review cycles.

Scope

Draft, fork-only for review. Behavioural change is purely editorial — no code or workflow impact. If you sign off, the same diff is a candidate to propose upstream against `OCA/OpenUpgrade:documentation`.

Companion PR for the commit-prefix Note is opened as a separate diff.

The current guide says lines can be reordered and grouped into a
"logical" block with a single consolidated comment. Recent reviewer
feedback consistently asks the opposite — each analysis line gets its
own inline marker, no consolidated author-blocks above multi-line
groups.

Update the Note to describe the inline-per-line convention and add a
short example showing the expected shape.
Align the annotation guidance with hbrunn's review on OCA#5647 ('don't add
this for empty lists') — empty work-file sections are left blank; only
populated sections get an inline # DONE / # NOTHING TO DO marker.
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