Skip to content

docs: add API policy and performance review guidance for agents - #27168

Merged
mbutrovich merged 3 commits into
apache:mainfrom
mbutrovich:agents-api-stabilityp-perf
Nov 10, 2026
Merged

mbutrovich merged 3 commits into
apache:mainfrom
mbutrovich:agents-api-stabilityp-perf

Conversation

@mbutrovich

@mbutrovich mbutrovich commented Nov 6, 2026 •

Copy link
Copy Markdown
Contributor

Which issue does this PR close?

  • N/A.

Rationale for this change

  • Seeing repeated undesired patterns from what look like agent-generated PRs and reviews that I'd like to cut down on.

What changes are included in this PR?

  • Adding some guidance based on recurring themes I am seeing across arrow-rs, iceberg-rust, and DataFusion (and its subprojects like datafusion-iceberg and Comet).

What is the testing strategy for this PR?

  • N/A.

Are there any user-facing changes?

No.

AI Disclosure

Claude Sonnet helped draft this, but I stand by the content.

@github-actions github-actions Bot added the documentation Improvements or additions to documentation label Nov 6, 2026
@mbutrovich
mbutrovich marked this pull request as ready for review November 6, 2026 17:00

@comphead comphead left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @mbutrovich looks good to me!

@alamb alamb left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @mbutrovich -- I agree this looks like great advice and codifies best practice

Comment thread AGENTS.md Outdated
- A PR merges as one squashed commit titled with the PR title, so it should do only what that title says. Put unrelated renames, reformatting, refactors, and drive-by fixes in a
separate PR.
- Default to no comment. Comment only what the code cannot say: invariants, non-obvious constraints, and why
a choice that looks wrong is right. Do not restate the code or describe how it changed. New public items get

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe we could suggest adding inline github review comments to describe how it is changed if needed

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea, done. The bullet now says to explain a change to reviewers in an inline PR review comment on the changed line.

Comment thread AGENTS.md

- A PR merges as one squashed commit titled with the PR title, so it should do only what that title says. Put unrelated renames, reformatting, refactors, and drive-by fixes in a
separate PR.
- Default to no comment. Comment only what the code cannot say: invariants, non-obvious constraints, and why

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍🏻

Comment thread AGENTS.md Resolved
@mbutrovich
mbutrovich added this pull request to the merge queue Nov 10, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Nov 10, 2026
@mbutrovich
mbutrovich added this pull request to the merge queue Nov 10, 2026
Merged via the queue into apache:main with commit baa243d Nov 10, 2026
45 checks passed
@mbutrovich
mbutrovich deleted the agents-api-stabilityp-perf branch November 10, 2026 21:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation v57.0.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants