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

Reviewers

Open
#31 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
api

Research direction

Start by reviewing the existing delegate handling and the patch API entry points to understand how review participants are represented. Done means the API exposes a unique reviewer list for each patch; displaying it in a summary pane is optional according to the issue.

Written by the indexing model from the issue text.

Description

enhancement

Overview

At the moment, patchwork has the concept of "delegates", or people to whom a patch has been assigned for review. However, patches often have reviewers who aren't delegates. These are tracked by way of comments, but it would be helpful to provide a way to gather a list of unique reviewers per patch and expose this via the API.

Dependencies

None.

Additional Work Items

Optionally, one could display this information in the summary pane on a patch page (or even on the patch list page).

Alternatives

We could rename "delegates" are "reviewers" and make them even less specific, i.e. anyone who follows up on a patch can be a delegate.

Useful resources

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.