Issue Linking

Open
#32 0 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 reviewing the Patchwork codebase to find how patches and commit messages are represented, then read the linked Gerrit, Launchpad, and GitHub resources. Done means Patchwork can generically identify issue links from commit messages and support multiple issue trackers, including Launchpad, GitHub Issues, and JIRA.

Written by the indexing model from the issue text.

Description

enhancement

Overview

Tools like Gerrit and GitHub allow you to link to an issue from a change. In both cases, this is done by searching the commit message for given strings. It would be helpful to do the same in Patchwork. This should be generic so that multiple issue trackers can be used. Some of the issue trackers I'd like to see supported include:

  • Launchpad
  • GitHub Issues
  • JIRA

Dependencies

None.

Additional Work Items

N/A

Alternatives

N/A

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.