aglinxinyuan opened a new pull request, #8675:
URL: https://github.com/apache/texera/pull/8675
### What changes were proposed in this PR?
Adds a claim check to the **Issues and PRs** section of `AGENTS.md`, so a
coding agent doesn't duplicate an issue someone else already claimed.
```
Before: file issue (unassigned) -> contributor /takes it + opens PR
-> agent's bundled PR also writes "Closes #N" -> merges first
-> merge-time credit step drops the contributor from the assignees
After: agent /takes what it files; before coding, and again before opening
the PR, it checks every issue its diff fixes, and leaves out any
taken one
```
| Change | Where |
| --- | --- |
| `/take` step added to the issue → PR flow diagram | diagram |
| "Claim before coding": an issue is **taken** if someone else is assigned,
or a linked PR is `OPEN` and someone else wrote it; the three `gh` commands
that check this | new bullet |
| Re-check right before opening the PR, for every issue the diff fixes
(closed or only related, each site of a bundled PR); if one is taken, leave out
that issue and its code change | "Reference the issue" bullet |
The linked-PR half of the check matters: GitHub drops the PR-opener
auto-assign for an outside contributor who never commented on the issue. So an
issue can show no assignee while it has an open PR (e.g. #6674 / #8603).
### Any related issues, documentation, discussions?
Related to #8149 and #8267.
### How was this PR tested?
Docs-only. Ran the new text's commands against `apache/texera`:
| Issue | Assignees | Linked PRs | Verdict |
| --- | --- | --- | --- |
| #6674 | none | #8603 (open, another author) | taken |
| #8674 | none | none | not taken |
`CONTRIBUTING.md#-comment-commands` resolves on the rendered page.
### Was this PR authored or co-authored using generative AI tooling?
Generated-by: Claude Code (Opus 5.5)
--
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]
