Restrict external automated contributions to triaged community issues - #12936
Open
brooke-hamilton wants to merge 8 commits into
Open
Restrict external automated contributions to triaged community issues#12936brooke-hamilton wants to merge 8 commits into
brooke-hamilton wants to merge 8 commits into
Conversation
Require external contributors using coding agents or bots to select triaged issues that are also marked help wanted or good first issue. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Signed-off-by: Brooke Hamilton <45323234+brooke-hamilton@users.noreply.github.com>
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
Keep the external automation policy limited to issue labels and existing assignment or pull request state. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Signed-off-by: Brooke Hamilton <45323234+brooke-hamilton@users.noreply.github.com>
Remove pre-triage pull request invitations and limit community contribution guidance to issues with the required eligibility labels. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Signed-off-by: Brooke Hamilton <45323234+brooke-hamilton@users.noreply.github.com>
Restore the existing contribution invitations for triaged, important, and good first issue labels while keeping them out of initial feature and maintenance responses. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Signed-off-by: Brooke Hamilton <45323234+brooke-hamilton@users.noreply.github.com>
Replace the remaining pick-it-up-sooner wording with a neutral pull request invitation. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Signed-off-by: Brooke Hamilton <45323234+brooke-hamilton@users.noreply.github.com>
Restore the welcome message and contribution guide link in the initial label responses while retaining the neutral pull request wording. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Signed-off-by: Brooke Hamilton <45323234+brooke-hamilton@users.noreply.github.com>
brooke-hamilton
enabled auto-merge
September 9, 2026 17:31
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
The changes are documentation/config-only, consistent across updated files, and the YAML/links appear correct with no functional code risk introduced.
Pull request overview
This PR tightens the repository’s contributor guidance to restrict external automated contributions (AI agents/coding bots) to only work on issues maintainers have already triaged and explicitly marked as community-friendly, reducing the chance of automation implementing unvetted or out-of-scope work.
Changes:
- Adds an explicit eligibility gate for external automation (triaged + help wanted/good first issue, unassigned, no existing PR) in core contributor entry points.
- Updates the “first PR” walkthrough to direct automated contributors to eligible issue searches.
- Removes urgency phrasing (“pick this item up sooner”) from the triage bot’s contribution invitations while keeping the contribution-guidelines link and welcoming tone.
File summaries
| File | Description |
|---|---|
AGENTS.md |
Adds the top-level automated contribution eligibility gate for repository agents and contributors. |
CONTRIBUTING.md |
Clarifies that only human contributors get the trivial-fix exception; automation is restricted to eligible triaged community issues. |
.github/configs/label-actions.yaml |
Adjusts bot-generated invitation wording to remove urgency while preserving contribution guidance links. |
docs/contributing/contributing-pull-requests/README.md |
Adds explicit automated eligibility prerequisites and acceptance checkpoint language. |
docs/contributing/contributing-code/contributing-code-first-commit/first-commit-06-creating-a-pr/index.md |
Updates the issue-picking step with links to eligible issue searches for automation. |
Review details
- Files reviewed: 5/5 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Contributor
|
One or more custom setup steps configured for this repository failed during this Copilot code review run: Setup steps run before each review. If the review above is missing context, or no review was posted at all, the failing step above may be the cause. See the workflow run for failure details, fix your setup steps configuration, and re-request a review. Note You can configure setup steps for Copilot code review separately from Copilot cloud agent with a |
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
Two contributor workflows omit assignment, existing-PR, and pre-submit re-check requirements.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Review details
- Files reviewed: 5/5 changed files
- Comments generated: 2
- Review effort level: Lite
| - The maintainers will respond to your issue, please work with the maintainers to ensure that what you're doing is in scope for the project before writing any code. | ||
| - For very minor changes like correcting a typo, human contributors may send a pull request without first opening an issue. | ||
| - For other changes, start by [choosing an existing issue](https://github.com/radius-project/radius/issues) or [opening an issue](https://github.com/radius-project/radius/issues/new/choose). | ||
| - External contributors using an AI agent, coding bot, or other automation must restrict their contributions to open issues labeled `triaged` and either `help wanted` or `good first issue`. The exception for minor changes does not apply to automated contributions. |
| At this point you've experienced the basic dev flow for the `rad` CLI. | ||
|
|
||
| It's time to pick an issue to work on! You can find a query [here](https://github.com/radius-project/radius/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22). | ||
| It's time to pick an issue to work on! External contributors using an AI agent, coding bot, or other automation must choose an open issue that is labeled `triaged` and either [`help wanted`](https://github.com/radius-project/radius/issues?q=is%3Aopen+is%3Aissue+label%3Atriaged+label%3A%22help+wanted%22) or [`good first issue`](https://github.com/radius-project/radius/issues?q=is%3Aopen+is%3Aissue+label%3Atriaged+label%3A%22good+first+issue%22). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Require external contributors using AI agents, coding bots, or other automation to work only on open issues labeled
triagedand eitherhelp wantedorgood first issue.The guidance also checks for existing assignments and pull requests and removes the trivial-fix exception for automated contributions. The triage bot continues to welcome community contributions and link to the contribution guidelines, but its invitations no longer suggest picking up an issue sooner.
Reason for change
Newly created issues can remain in triage for up to a week. External automation can otherwise begin implementation and open pull requests before maintainers determine whether an issue is actionable or in scope. The triage bot's urgency-oriented wording could reinforce that behavior even though its general community-contribution guidance remains valid.
How to test
AGENTS.mdand the contributor documentation.triagedand the selected community-contribution label..github/configs/label-actions.yamlparses as YAML, all five contribution invitations retain the welcome text and contribution-guidelines link, and no response containspick this item up sooner.cspell lint --config ./.github/linters/.cspell.yml --no-progress AGENTS.md CONTRIBUTING.md docs/contributing/contributing-pull-requests/README.md docs/contributing/contributing-code/contributing-code-first-commit/first-commit-06-creating-a-pr/index.md.File change summary
AGENTS.mdCONTRIBUTING.md.github/configs/label-actions.yamldocs/contributing/contributing-pull-requests/README.mddocs/contributing/contributing-code/contributing-code-first-commit/first-commit-06-creating-a-pr/index.md