Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Per-project sender blacklist

Open
#323 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start by tracing how incoming patches are associated with projects and where sender filtering could be applied. Review the project configuration and patch-ingestion paths, then define how maintainers configure blocked senders per project. Done means matching patches are excluded without affecting other projects, with coverage for the filtering behavior.

Written by the indexing model from the issue text.

Description

enhancement

Sometimes we want to block patches from certain senders (e.g. bots that are irrelevant for a certain kernel subsystem but end up Cc-ing them anyway) from appearing as patches in patchwork.

Would be helpful to be able to block these patches on a per-project basis so that different maintainers can make different decisions.

(@mpe)

Dominant language
Python
Stars
317
Forks
91
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getpatchwork/patchwork

All issues in getpatchwork/patchwork

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.