andygrove opened a new pull request, #6734:
URL: https://github.com/apache/datafusion-comet/pull/6734
## Which issue does this PR close?
N/A (contributor documentation).
## Rationale for this change
Many Comet contributors use AI tools to write pull requests and to review
them, but apart from a few tips the contributor guide doesn't say how the
project expects them to be used.
Automated reviews are useful and often catch real problems. An approval is
different. It is a person's judgment that a change is ready to merge, and a
tool can't take responsibility for that. GitHub counts an approval that a tool
posts under a committer's account the same as one the committer gave, so the
guide needs to say plainly that every approval must come from a human who
reviewed the change.
## What changes are included in this PR?
- A new page, `docs/source/contributor-guide/ai_assisted_contributions.md`,
in the Getting Started section. It covers three things:
- Writing code with AI tools. The author owns the change whatever wrote
it, understands it end to end, points out what they are unsure of, and tests it
against Spark. This follows DataFusion's policy on AI-assisted contributions,
and the page links to it and to the ASF's generative tooling guidance.
- Automated reviews. They are a useful first pass and should be treated
like any reviewer's comments, but a clean one is not evidence that a change is
correct.
- Approvals. Every approval must come from a human who reviewed the
change. A review tool that posts under someone's GitHub account should post
comment reviews only, and committers should not merge on the strength of a
tool's approval.
- A short "Using AI tools" section in `contributing.md` that links to the
page.
- An entry in `AGENTS.md` that tells coding agents never to approve a pull
request on their own judgment, even when asked to approve it if it looks good,
so agents working in the repository pick up the rule.
## How are these changes tested?
- `prettier --check` (3.9.9) passes on the changed files.
- I did not build the Sphinx site locally. The new toctree entry follows the
existing ones in `index.md`.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
