Improve interoperability with GitGitGadget

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
git, github
Domain
api, backend

Research direction

Start with the linked Git mailing-list report and the Patchwork Git instance, then review how submissions from GitGitGadget are represented. The issue does not name implementation files or tests; done would require an agreed approach that preserves each GitGitGadget submitter's identity in Patchwork.

Written by the indexing model from the issue text.

Description

enhancement

GitGitGadget is a GitHub app that can be used to send patch series to the Git mailing list using GitHub PRs (for now it works only for the Git mailing list, I think some Linux subsystems are thinking of using it eventually, though I don't remember where exactly on the Git mailing list I've read that).

At the moment, because of the way GitGitGadget works (all series sent to the list use gitgitgadget@gmail.com in the "From" header, and record the submitter identity ), all series sent using this tool show up on the Git patchwork instance as originating from the same contributor, i.e. the person that most recently used the tool at any given time.

I reported that on the Git mailing list here, and it was not clear if it would be better to fix this interoperability problem on the patchwork side or on GitGitGadget's side.

So I'm opening an issue here so that it can be discussed.

@dscho @gitster

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.