CI request: forbid @mentions in commit messages/descriptions
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
I would much appreciate it if a CI step was added that checks for and forbids @mentions being included in commit messages/descriptions.
If such a commit is merged into the Rust repository, then you will receive an additional notification every single time this commit gets merged/replayed into any fork. It is incredibly frustrating, and can't be protected against (to my knowledge) by unfollowing the issue/PR as each merge consists of a completely new mention as far as Github is concerned, possibly from many different repositories. It is, essentially, an unintended spam amplification attack.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the Rust repository's existing CI configuration and checks to find where commit messages or descriptions are validated. Determine how the check should handle @mentions across the requested commit metadata, then verify that the CI step rejects matching commits without disrupting normal commits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100