[jira] [Updated] (CAMEL-24492) Document that backport PRs (cherry-picks of an already-reviewed main PR) do not need reviewers and can be merged as-is

["Claus Ibsen (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-24492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-24492:
--------------------------------
    Fix Version/s: 4.23.0

> Document that backport PRs (cherry-picks of an already-reviewed main PR) do not need reviewers and can be merged as-is
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-24492
>                 URL: https://issues.apache.org/jira/browse/CAMEL-24492
>             Project: Camel
>          Issue Type: Improvement
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 4.23.0
>
>
> CLAUDE.md's "PR Reviewers" section currently says every PR that is ready for review should have reviewers requested from active committers. This does not account for backport PRs.
> When a PR is a straight backport (cherry-pick) of a PR that was already reviewed and merged on main to an older LTS maintenance branch (e.g. camel-4.14.x, camel-4.18.x), the code change has already gone through human review on main. Requesting fresh reviewers on the backport PR duplicates that review for no benefit and adds friction to the backport workflow.
> Proposed clarification to CLAUDE.md's "PR Reviewers" / merge-related guidance:
> - A backport PR must NOT be assigned any reviewers.
> - A backport PR may be merged as-is (once CI is green) without requiring a new human approval, since the change was already reviewed on the PR it was backported from.
> This should be added as an explicit carve-out alongside the existing "PR Reviewers" and "Merge Requirements" sections in CLAUDE.md.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)