Skip to content

docs: add spam policy and saved reply#32957

Merged
alan-agius4 merged 2 commits intoangular:mainfrom
alan-agius4:spam-policy
Apr 8, 2026
Merged

docs: add spam policy and saved reply#32957
alan-agius4 merged 2 commits intoangular:mainfrom
alan-agius4:spam-policy

Conversation

@alan-agius4
Copy link
Copy Markdown
Collaborator

@alan-agius4 alan-agius4 commented Apr 8, 2026

Introduces a new spam policy in CONTRIBUTING.md limiting community contributors to no more than 3 open PRs simultaneously to better manage team resources and triage efforts. Also adds a corresponding saved reply for closing excessive issues/PRs.

@alan-agius4 alan-agius4 requested a review from dgp1130 April 8, 2026 07:05
@alan-agius4 alan-agius4 added action: review The PR is still awaiting reviews from at least one requested reviewer target: patch This PR is targeted for the next patch release labels Apr 8, 2026
@angular-robot angular-robot bot added the area: docs Related to the documentation label Apr 8, 2026
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a Spam Policy to the CONTRIBUTING.md file and adds a corresponding saved reply template in .github/SAVED_REPLIES.md. The policy limits community contributors to three open pull requests at a time to better manage team resources. Review feedback identifies several typos, a missing comma for readability, and broken internal anchor links that require correction.

@alan-agius4 alan-agius4 force-pushed the spam-policy branch 3 times, most recently from e91c4c1 to 9a85c65 Compare April 8, 2026 07:39
Introduces a new spam policy in CONTRIBUTING.md limiting community contributors to no more than 3 open PRs simultaneously to better manage team resources and triage efforts. Also adds a corresponding saved reply for closing excessive issues/PRs.
Copy link
Copy Markdown
Collaborator

@dgp1130 dgp1130 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FWIW, I don't think we need the policy to be listed here in order to invoke it in the CLI repo, but no objection to including it.

It does make me wonder if we should instead just link to the angular/angular repo and say "We follow all the policies specified over there" so we don't have to deal with syncing them across the repos.

@alan-agius4
Copy link
Copy Markdown
Collaborator Author

@dgp1130 agreed.

@alan-agius4 alan-agius4 added action: merge The PR is ready for merge by the caretaker and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Apr 8, 2026
@alan-agius4 alan-agius4 merged commit feafdbd into angular:main Apr 8, 2026
11 checks passed
@alan-agius4 alan-agius4 deleted the spam-policy branch April 8, 2026 16:12
@alan-agius4
Copy link
Copy Markdown
Collaborator Author

This PR was merged into the repository. The changes were merged into the following branches:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

action: merge The PR is ready for merge by the caretaker area: docs Related to the documentation target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants