This is an automated email from the ASF dual-hosted git repository. davsclaus pushed a commit to branch feature/CAMEL-24492-backport-no-reviewers in repository https://gitbox.apache.org/repos/asf/camel.git
commit de4eddc8f9f56642b9c92f9316fb7ed82f038fbf Author: Claus Ibsen <[email protected]> AuthorDate: Wed Aug 26 07:31:41 2026 +0200 CAMEL-24492: Document that backport PRs need no reviewers and can be merged as-is A backport PR that cherry-picks an already-reviewed, already-merged main PR onto an LTS maintenance branch duplicates review effort for no benefit if it requires fresh reviewers before merging. Clarify that such PRs must not be assigned reviewers and may be merged once CI is green, without a new human approval - unless the backport needed manual conflict resolution beyond a mechanical cherry-pick, in which case normal review applies. Co-Authored-By: Claude Sonnet 5 <[email protected]> Signed-off-by: Claus Ibsen <[email protected]> --- AGENTS.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index 0c2c1ef1aa48..d15354135473 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -75,6 +75,21 @@ marked ready for review. - For cross-cutting changes (core, API), include committers with broader project knowledge. - Request review from **at least 2 relevant committers** using `gh pr edit --add-reviewer`. - When all comments on the Pull Request are addressed (by providing a fix or providing more explanation) and the PR checks are green, re-request review on existing reviewers so that they are aware that the new changeset is ready to be reviewed. +- **Exception — backport PRs:** do not request reviewers on a PR that is a straight backport + (cherry-pick) of a PR already reviewed and merged on `main`. See "Backport PRs" below. + +### Backport PRs + +A backport PR that cherry-picks a commit from a PR already reviewed and merged on `main` onto an +older LTS maintenance branch (e.g. `camel-4.14.x`, `camel-4.18.x`) does not need a fresh review — +the code change already went through human review on the PR it was backported from. + +- A backport PR MUST NOT be assigned any reviewers. +- A backport PR MAY be merged as-is, once CI is green, without waiting for a new human approval. + This is the one exception to the "at least one human approval" rule in "Merge Requirements" below. +- This exception applies only to straight cherry-picks. If a backport required manual conflict + resolution that changed the code beyond a mechanical port, treat it as a normal PR and request + review. ### Doing a review
