This is an automated email from the ASF dual-hosted git repository.
lidavidm pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/arrow-adbc.git
The following commit(s) were added to refs/heads/main by this push:
new cf721c46cc docs: try to head off antisocial agentic behavior in
AGENTS.md (#4978)
cf721c46cc is described below
commit cf721c46cc6bd293267dd5146e37d7a76c1ea9c4
Author: David Li <[email protected]>
AuthorDate: Sat Oct 31 20:10:14 2026 -0700
docs: try to head off antisocial agentic behavior in AGENTS.md (#4978)
We may also want to take inspiration from apache/arrow:
https://github.com/apache/arrow/pull/50375
---
AGENTS.md | 34 ++++++++++++++++++++++++++++++++++
1 file changed, 34 insertions(+)
diff --git a/AGENTS.md b/AGENTS.md
index b31518f3d7..9a57f27f32 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -21,3 +21,37 @@
You must follow the guidance around pull requests and commits in
@CONTRIBUTING.md.
+
+## Commit Messages and Pull Request Descriptions
+
+Do not repeat the PR title (and do not repeat the Conventional Commits
+header).
+
+Be brief. Do not list files changed, and do not summarize changes made unless
+there are _significant_ design decisions made.
+
+Do not list tests added, run, or not run, and do not talk about "test
+plans". If you did not run a test or were not able to, do not submit the pull
+request: the tests must be run, and you are capable of accomplishing this. The
+project has limited CI resources and we are not a substitute for your personal
+machine. If you added a test and were not able to run it, remove the test.
+Note that `git diff`, `pre-commit`, etc. do not count as proper tests. Do not
+talk about running or checking those, but make sure that they pass before
+committing or submitting.
+
+You must disclose AI usage via the `Generated-by` or `Assisted-by` Git trailer
+(because the description will be used as the commit message).
+
+The motivation/problem should be documented by the linked GitHub issue
+already; if there is no issue then a very brief description of the rationale
+for the change is acceptable.
+
+Do not talk about rebasing, multiple commits, or other branches, repositories,
+or pull requests unless they are directly relevant to the content of the pull
+request. For example, if you submitted multiple pull requests but they may
+conflict, this is not a reason to mention it in the description.
+
+You should perform a code review of your submission before creating a pull
+request, and you should ask your human handler to review as well. Submissions
+that do not substantatively engage with the maintainers and respect their time
+are likely to be closed without review.
