2026-04-03 10:20:55 -07:00
|
|
|
# Spam Policy
|
|
|
|
|
|
|
|
|
|
Users who create excessive amounts of issues or PRs in a short time frame,
|
2026-04-08 07:20:34 +00:00
|
|
|
particularly low-quality or low-value contributions, may see those contributions
|
2026-04-03 10:20:55 -07:00
|
|
|
automatically closed without consideration.
|
|
|
|
|
|
|
|
|
|
Community contributors should limit themselves to no more than 3 open PRs at a
|
|
|
|
|
single time.
|
|
|
|
|
|
|
|
|
|
## Why?
|
|
|
|
|
|
2026-04-08 07:20:34 +00:00
|
|
|
Reviewing and shepherding PRs as well as managing large issue counts takes time
|
2026-04-03 10:20:55 -07:00
|
|
|
and energy from the core team. Triaging a PR well enough to understand its goals
|
|
|
|
|
and implementation takes a significant amount of time, regardless of whether the
|
|
|
|
|
PR is ultimately accepted. This policy ensures the team is able to balance its
|
|
|
|
|
limited resources across all contributors and projects.
|
|
|
|
|
|
|
|
|
|
## Exceptions
|
|
|
|
|
|
|
|
|
|
If you plan to undertake more significant work that you anticipate will generate
|
|
|
|
|
many individual PRs, please reach out to the team in a Github issue first to
|
|
|
|
|
validate that Angular will be able to support and accept your contributions.
|
