Skip to content

[MINOR][DOCS] Use AGENTS.md for nested project instructions #57501

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
cloud-fan wants to merge 1 commit into
base: master
Choose a base branch
from
+6 −0
Open

[MINOR][DOCS] Use AGENTS.md for nested project instructions #57501

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -235,6 +235,12 @@ DO NOT force push or use `--amend` on pushed commits unless the user explicitly

Always get user approval before external operations such as pushing commits, creating PRs, or posting comments. Use `gh pr create` to open PRs. If `gh` is not installed, generate the GitHub PR URL for the user and recommend installing the GitHub CLI.

## Project Instructions Discovery

When exploring or working in any directory, always check for nested `AGENTS.md` files in that
directory and its ancestors. Read and follow every applicable file; instructions in a more specific
directory take precedence for that directory's scope.

## Versioning and Branch Policy

When a change needs a version — `@since` annotations, config `.version("...")` (`SQLConf` / `*Conf`), new `MimaExcludes` sections, etc. — use the version of the branch it first ships in, with `-SNAPSHOT` stripped. Determine that branch:
Expand Down