This is an automated email from the ASF dual-hosted git repository.
spetz pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/iggy.git
The following commit(s) were added to refs/heads/master by this push:
new 815f345b3 docs: require agent review, comment replies and fewer
rebases (#4384)
815f345b3 is described below
commit 815f345b3242489e523ee62b990a29048e77dc91
Author: Hubert Gruszecki <[email protected]>
AuthorDate: Fri Oct 2 21:03:51 2026 +0200
docs: require agent review, comment replies and fewer rebases (#4384)
Human review time went to defects that an agent review can find
first. Some review comments got no answer. Rebases without a
conflict re-ran CI on the GitHub Actions runners that all Apache
projects share.
Strict status checks already make a maintainer update the branch
before the squash merge, so authors update it only on a conflict
or when asked.
---
CONTRIBUTING.md | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 5cec59d59..e8e99f429 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -37,6 +37,11 @@ not. Before you open a PR you must be able to explain what
every part of the cha
and why, answer review questions about it yourself, and defend the design
without going
back to the tool for an answer. If you can't, the PR isn't ready.
+If an AI assistant helped you write the change, review it with the
+[`team-review-slim`](.claude/skills/team-review-slim/SKILL.md) skill before
you open the PR.
+The skill can report false findings. Fix every finding that is correct and
that applies to
+your change.
+
While you're new to the project, please keep to **one open PR at a time**.
Review takes
longer than writing, so a queue of changes from one contributor holds up
everyone else's.
@@ -64,6 +69,23 @@ for review.
One PR = one thing. Bug fix, refactor, feature - separate PRs. Mixed PRs will
be closed.
+### Review Comments
+
+Respond to every review comment, so that the reviewer knows you read it. Any
one of these
+is enough:
+
+- Resolve the conversation
+- React with 👍
+- Reply to the comment
+
+### Updating Your Branch
+
+Do not rebase your branch or merge `master` into it only to keep it up to
date. Each push
+runs CI again on GitHub Actions runners that all Apache projects share. A
maintainer
+updates the branch before the merge.
+
+If GitHub reports a merge conflict, or if a maintainer asks you to, update
your branch.
+
### Quality Checks
For Rust code:
