Use database-defined Tags when extracting tags for generating mbox

Open
#151 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start at the code path that generates an mbox and extracts tags from comments, then trace how tags defined in the database are represented. Verify the behavior with the existing mbox-generation tests, or add coverage if none is present; done means database-defined tags such as Fixes: are included alongside the existing tags.

Written by the indexing model from the issue text.

Description

enhancement

Right now, the way we combine tags when generating an mbox is by looping through all of the comments and matching:

^(Tested|Reviewed|Acked|Signed-off|Nacked|Reported)-by: .*$

This completely ignores custom tags defined in the database, e.g. Fixes:.

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.