Skip to content
Sending GitHub PRs to the Git mailing list
TypeScript Shell JavaScript Batchfile
Branch: master
Clone or download
dscho Merge pull request #105 from gitgitgadget/dependabot/npm_and_yarn/lod…

build(deps): bump lodash from 4.17.11 to 4.17.14
Latest commit f4c667c Jul 11, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.vscode ci: greet new GitGitGadget users Jan 14, 2019
azure-function Add an Azure Function to back the GitGitGadget GitHub App Dec 21, 2018
images Make icon look better Jun 2, 2018
lib Merge pull request #101 from webstech/Trim-trailing-white-space-in-co… Jul 10, 2019
res ci: greet new GitGitGadget users Jan 14, 2019
script Expose the public-inbox/git processing via the command-line helper Apr 12, 2019
tests Quote names in emails if necessary Jun 25, 2019
.deployment Add the deployment script for Azure Web Apps Jun 8, 2018
.editorconfig Add an .editorconfig file May 29, 2018
.gitattributes Add a GitGitGadget logo Jun 2, 2018
.gitignore Support 'npm run ci' for Continuous Integration Dec 26, 2018 Initialize a Probot Jun 2, 2018 Merge pull request #61 CONTRIBUTING: we do not actually use Standard … Dec 26, 2018 Correct links to remove '.' causing 404. May 14, 2019
LICENSE Initialize a Probot Jun 2, 2018 README: streamline beginning, fix Markdown issues Jan 10, 2019 Update TODOs Dec 25, 2018
azure-pipelines.yml Merge pull request #64 ci: upgrade to node.js v10.x Dec 26, 2018
deploy.cmd Add the deployment script for Azure Web Apps Jun 8, 2018
package-lock.json build(deps): bump lodash from 4.17.11 to 4.17.14 Jul 11, 2019
package.json Upgrade Typescript to latest version Jul 11, 2019
tsconfig.json tslint/tsconfig: avoid new deprecation warning Nov 5, 2018
tslint.json Adjust formatting rules Dec 21, 2018

Contributing git.git patches via GitHub PRs

This project's goal is to make contributions to the Git project (almost) as easy as opening a GitHub PR. The idea is for users to open a Pull Request at

with a good description of their patch series. Then, the command /submit, issued via a comment on said PR will tell GitGitGadget to send the patches as mail thread to the Git mailing list, with the Pull Request's description as cover letter.

As is common, reviewers on the Git mailing list will probably ask for modifications. These should be folded into the respective commits (or inserted as stand-alone commits at an appropriate place in the patch series) via git rebase -i, followed by a force-push. Once everything is in a good shape, update the description to include information about changes performed relative to the latest patch series iteration, and then another /submit will ask GitGitGadget to send a new iteration of the patch series.

All relevant information, such as the current iteration of the patch series, the Message-ID of the sent mails, etc is stored in the Git notes in refs/notes/gitgitgadget.

Note: GitGitGadget will Cc: the original authors when sending patches on their behalf, and people mentioned in the Cc: footer of the Pull Request description.

Furthermore, for all iterations of a patch series but the first one, GitGitGadget will insert a machine-generated representation of what changed, and reply to the cover letter of the previous iteration.

For convenience of reviewers, GitGitGadget will generate tags for each iteration it sent, and push those to Links to those tags will be included in the cover letter.

You can’t perform that action at this time.