{"thread":{"id":"46148","subject":"[PATCH v1] Configure Git contribution guidelines for github.com","startedAt":"2017-06-09T14:23:40Z","lastAt":"2017-06-15T17:59:21Z","messageCount":17,"participants":["Lars Schneider","Ævar Arnfjörð Bjarmason","Jonathan Nieder","Junio C Hamano","Jeff King","Philip Oakley","Andreas Heiduk"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"321830","messageId":"20170609142151.94811-1-larsxschneider@gmail.com","threadId":"46148","inReplyTo":null,"subject":"[PATCH v1] Configure Git contribution guidelines for github.com","fromName":"Lars Schneider","fromEmail":"larsxschneider@gmail.com","sentAt":"2017-06-09T14:21:51Z","receivedAt":"2017-06-09T14:23:40Z","isPatch":true,"sender":{"key":"larsxschneider@gmail.com","avatar":"https://avatars.githubusercontent.com/u/477434?v=4"},"body":"Many open source projects use github.com for their contribution process.\nAlthough we mirror the Git core repository to github.com [1] we do not\nuse any other github.com service. This is unknown/unexpected to a\nnumber of (potential) contributors and consequently they create Pull\nRequests against our mirror with their contributions. These Pull\nRequests become stall [2]. This is frustrating to them as they think we\nignore them and it is also unsatisfactory for us as we miss potential\ncode improvements and/or new contributors.\n\nGitHub offers a way to notify Pull Request contributors about the\ncontribution guidelines for a project [3]. Let's make use of this!\n\n[1] https://github.com/git/git\n[2] https://github.com/git/git/pulls\n[3] https://help.github.com/articles/creating-a-pull-request-template-for-your-repository/\n\nSigned-off-by: Lars Schneider \n---\n\nHi,\n\nI am perfectly aware that adding a \".github\" directory in the Git core\ntree is ugly. However, I believe the benefits (\"well informed new\ncontributors\") outweigh the injury.\n\nYou can see how a github.com Pull Request creation window would like here:\nhttps://github.com/larsxschneider/git/compare/master...larsxschneider-patch-1?quick_pull=1\n\nI added a link that jumps to a part my GitMerge 2017 talk which explains\nGit core contributions from my point view. Although I tried my best, the\npresentation is not perfect and might not reflect the view of the Git\ncommunity. I wouldn't have a problem at all with removing the link.\n\nI also did not break the lines in the .github/*.md files as I thought it\nrenders nicer on the github.com web interface. I am happy to change that,\ntoo, though.\n\nCheers,\nLars\n\n\nNotes:\n Base Ref: master\n Web-Diff: https://github.com/larsxschneider/git/commit/d859be5016\n Checkout: git fetch https://github.com/larsxschneider/git contrib-guide-v1 && git checkout d859be5016\n\n .github/CONTRIBUTING.md | 10 ++++++++++\n .github/PULL_REQUEST_TEMPLATE.md | 3 +++\n 2 files changed, 13 insertions(+)\n create mode 100644 .github/CONTRIBUTING.md\n create mode 100644 .github/PULL_REQUEST_TEMPLATE.md\n\ndiff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md\nnew file mode 100644\nindex 0000000000..8d01be6a71\n--- /dev/null\n+++ b/.github/CONTRIBUTING.md\n@@ -0,0 +1,10 @@\n+## Contributing to Git\n+\n+Thanks for taking the time to contribute to Git! Please be advised, that the Git community does not use github.com for their contributions. Instead, we use a [mailing list](http://public-inbox.org/git/) for code submissions, code reviews, and bug reports.\n+\n+Please [read the maintainer notes](http://repo.or.cz/w/git.git?a=blob_plain;f=MaintNotes;hb=todo) to learn how the Git\n+project is managed, and how you can work with it. In addition, we highly recommend you to [read our submission guidelines](../Documentation/SubmittingPatches).\n+\n+If you prefer video, then [this talk](https://www.youtube.com/watch?v=Q7i_qQW__q4&feature=youtu.be&t=6m4s) might be useful to you as the presenter walks you through the contribution process by example.\n+\n+Your Git community\ndiff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md\nnew file mode 100644\nindex 0000000000..c737a64620\n--- /dev/null\n+++ b/.github/PULL_REQUEST_TEMPLATE.md\n@@ -0,0 +1,3 @@\n+Thanks for taking the time to contribute to Git! Please be advised, that the Git community does not use github.com for their contributions. Instead, we use a mailing list for code submissions, code reviews, and bug reports.\n+\n+Please read the \"guidelines for contributing\" linked above!\n\nbase-commit: 8d1b10321b20bd2a73a5b561cfc3cf2e8051b70b\n--\n2.13.0\n\n"},{"id":"321835","messageId":"CACBZZX7O9DgLGOHKhojZRi7n=j3X0W9B_sRGLi6cBpc74GLyeg@mail.gmail.com","threadId":"46148","inReplyTo":"20170609142151.94811-1-larsxschneider@gmail.com","subject":"Re: [PATCH v1] Configure Git contribution guidelines for github.com","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2017-06-09T16:18:13Z","receivedAt":"2017-06-09T16:18:41Z","isPatch":true,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"On Fri, Jun 9, 2017 at 4:21 PM, Lars Schneider wrote:\n> Many open source projects use github.com for their contribution process.\n> Although we mirror the Git core repository to github.com [1] we do not\n> use any other github.com service. This is unknown/unexpected to a\n> number of (potential) contributors and consequently they create Pull\n> Requests against our mirror with their contributions. These Pull\n> Requests become stall [2]. This is frustrating to them as they think we\n> ignore them and it is also unsatisfactory for us as we miss potential\n> code improvements and/or new contributors.\n>\n> GitHub offers a way to notify Pull Request contributors about the\n> contribution guidelines for a project [3]. Let's make use of this!\n>\n> [1] https://github.com/git/git\n> [2] https://github.com/git/git/pulls\n> [3] https://help.github.com/articles/creating-a-pull-request-template-for-your-repository/\n\nIt would be good to have some instructions, but instead of warning\npeople off we could just point them to submitgit.herokuapp.com\n\nYou can submit patches to this list using that, and if someone's\ntrying to submit a pull request they might be much happier using that.\n\nE.g. here's one I made recently https://github.com/git/git/pull/362\nand the resulting patch on the ML:\nhttps://public-inbox.org/git/0102015c492e27c6-669f7ca8-e7c6-484f-9c5b-7cb9358ee966-000000@eu-west-1.amazonses.com/\n\n>\n> Signed-off-by: Lars Schneider \n> ---\n>\n> Hi,\n>\n> I am perfectly aware that adding a \".github\" directory in the Git core\n> tree is ugly. However, I believe the benefits (\"well informed new\n> contributors\") outweigh the injury.\n>\n> You can see how a github.com Pull Request creation window would like here:\n> https://github.com/larsxschneider/git/compare/master...larsxschneider-patch-1?quick_pull=1\n>\n> I added a link that jumps to a part my GitMerge 2017 talk which explains\n> Git core contributions from my point view. Although I tried my best, the\n> presentation is not perfect and might not reflect the view of the Git\n> community. I wouldn't have a problem at all with removing the link.\n>\n> I also did not break the lines in the .github/*.md files as I thought it\n> renders nicer on the github.com web interface. I am happy to change that,\n> too, though.\n>\n> Cheers,\n> Lars\n>\n>\n> Notes:\n> Base Ref: master\n> Web-Diff: https://github.com/larsxschneider/git/commit/d859be5016\n> Checkout: git fetch https://github.com/larsxschneider/git contrib-guide-v1 && git checkout d859be5016\n>\n> .github/CONTRIBUTING.md | 10 ++++++++++\n> .github/PULL_REQUEST_TEMPLATE.md | 3 +++\n> 2 files changed, 13 insertions(+)\n> create mode 100644 .github/CONTRIBUTING.md\n> create mode 100644 .github/PULL_REQUEST_TEMPLATE.md\n>\n> diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md\n> new file mode 100644\n> index 0000000000..8d01be6a71\n> --- /dev/null\n> +++ b/.github/CONTRIBUTING.md\n> @@ -0,0 +1,10 @@\n> +## Contributing to Git\n> +\n> +Thanks for taking the time to contribute to Git! Please be advised, that the Git community does not use github.com for their contributions. Instead, we use a [mailing list](http://public-inbox.org/git/) for code submissions, code reviews, and bug reports.\n> +\n> +Please [read the maintainer notes](http://repo.or.cz/w/git.git?a=blob_plain;f=MaintNotes;hb=todo) to learn how the Git\n> +project is managed, and how you can work with it. In addition, we highly recommend you to [read our submission guidelines](../Documentation/SubmittingPatches).\n> +\n> +If you prefer video, then [this talk](https://www.youtube.com/watch?v=Q7i_qQW__q4&feature=youtu.be&t=6m4s) might be useful to you as the presenter walks you through the contribution process by example.\n> +\n> +Your Git community\n> diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md\n> new file mode 100644\n> index 0000000000..c737a64620\n> --- /dev/null\n> +++ b/.github/PULL_REQUEST_TEMPLATE.md\n> @@ -0,0 +1,3 @@\n> +Thanks for taking the time to contribute to Git! Please be advised, that the Git community does not use github.com for their contributions. Instead, we use a mailing list for code submissions, code reviews, and bug reports.\n> +\n> +Please read the \"guidelines for contributing\" linked above!\n>\n> base-commit: 8d1b10321b20bd2a73a5b561cfc3cf2e8051b70b\n> --\n> 2.13.0\n>\n"},{"id":"321838","messageId":"F9939C5D-C710-4788-81A0-4D7958971128@gmail.com","threadId":"46148","inReplyTo":"CACBZZX7O9DgLGOHKhojZRi7n=j3X0W9B_sRGLi6cBpc74GLyeg@mail.gmail.com","subject":"Re: [PATCH v1] Configure Git contribution guidelines for github.com","fromName":"Lars Schneider","fromEmail":"larsxschneider@gmail.com","sentAt":"2017-06-09T16:29:27Z","receivedAt":"2017-06-09T16:29:35Z","isPatch":true,"sender":{"key":"larsxschneider@gmail.com","avatar":"https://avatars.githubusercontent.com/u/477434?v=4"},"body":"\n> On 09 Jun 2017, at 18:18, Ævar Arnfjörð Bjarmason wrote:\n> \n> On Fri, Jun 9, 2017 at 4:21 PM, Lars Schneider wrote:\n>> Many open source projects use github.com for their contribution process.\n>> Although we mirror the Git core repository to github.com [1] we do not\n>> use any other github.com service. This is unknown/unexpected to a\n>> number of (potential) contributors and consequently they create Pull\n>> Requests against our mirror with their contributions. These Pull\n>> Requests become stall [2]. This is frustrating to them as they think we\n>> ignore them and it is also unsatisfactory for us as we miss potential\n>> code improvements and/or new contributors.\n>> \n>> GitHub offers a way to notify Pull Request contributors about the\n>> contribution guidelines for a project [3]. Let's make use of this!\n>> \n>> [1] https://github.com/git/git\n>> [2] https://github.com/git/git/pulls\n>> [3] https://help.github.com/articles/creating-a-pull-request-template-for-your-repository/\n> \n> It would be good to have some instructions, but instead of warning\n> people off we could just point them to submitgit.herokuapp.com\n> \n> You can submit patches to this list using that, and if someone's\n> trying to submit a pull request they might be much happier using that.\n\nAgreed! I wasn't sure if this solution is still active/maintained by Roberto!\n\n- Lars"},{"id":"321843","messageId":"20170609170357.GE21733@aiede.mtv.corp.google.com","threadId":"46148","inReplyTo":"20170609142151.94811-1-larsxschneider@gmail.com","subject":"Re: [PATCH v1] Configure Git contribution guidelines for github.com","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2017-06-09T17:03:57Z","receivedAt":"2017-06-09T17:04:07Z","isPatch":true,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Hi,\n\nSome mostly nitpicky initial thoughts. Thanks for writing this.\n\nLars Schneider wrote:\n\n> Many open source projects use github.com for their contribution process.\n> Although we mirror the Git core repository to github.com [1] we do not\n> use any other github.com service. This is unknown/unexpected to a\n> number of (potential) contributors and consequently they create Pull\n> Requests against our mirror with their contributions. These Pull\n> Requests become stall [2]. This is frustrating to them as they think we\n> ignore them and it is also unsatisfactory for us as we miss potential\n> code improvements and/or new contributors.\n\nI think this description could be more focused. It's also not\nself-contained --- e.g. the link to stalled pull requests is likely to\nbecome stale over time, especially if GitHub gives us a way to disable\npull requests for the repository some day.\n\nCould you summarize for me the motivation behind this patch? Is it to\nmake Git more approachable, to avoid frustrating contributors, etc?\n\n[...]\n> I am perfectly aware that adding a \".github\" directory in the Git core\n> tree is ugly. However, I believe the benefits (\"well informed new\n> contributors\") outweigh the injury.\n> \n> You can see how a github.com Pull Request creation window would like here:\n> https://github.com/larsxschneider/git/compare/master...larsxschneider-patch-1?quick_pull=1\n> \n> I added a link that jumps to a part my GitMerge 2017 talk which explains\n> Git core contributions from my point view. Although I tried my best, the\n> presentation is not perfect and might not reflect the view of the Git\n> community. I wouldn't have a problem at all with removing the link.\n> \n> I also did not break the lines in the .github/*.md files as I thought it\n> renders nicer on the github.com web interface. I am happy to change that,\n> too, though.\n\nThis discussion is much clearer to me than the commit message.\n\nI've found that often happens to me when writing patches, too.\nSometimes after proofreading I completely replace the initial\ndescription that I wrote at commit time with what I came up later and\nwas going to put after the three-dash delimiter.\n\nWould putting a PULL_REQUEST_TEMPLATE and CONTRIBUTING in the\ntop-level directory work? If I'm reading\nhttps://help.github.com/articles/setting-guidelines-for-repository-contributors/#adding-a-contributing-file\ncorrectly then it seems to say the \".github/\" prefix is optional.\n\nI also find the long source lines hard to read. Can you say more\nabout how broken lines render in the github.com web interface? I\nwould have expected github's markdown renderer to behave like others\nand cope with line wrapping.\n\nThanks and hope that helps,\nJonathan\n"},{"id":"321866","messageId":"xmqqy3t04nx1.fsf@gitster.mtv.corp.google.com","threadId":"46148","inReplyTo":"CACBZZX7O9DgLGOHKhojZRi7n=j3X0W9B_sRGLi6cBpc74GLyeg@mail.gmail.com","subject":"Re: [PATCH v1] Configure Git contribution guidelines for github.com","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2017-06-10T01:44:10Z","receivedAt":"2017-06-10T01:44:21Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Ævar Arnfjörð Bjarmason writes:\n\n> On Fri, Jun 9, 2017 at 4:21 PM, Lars Schneider wrote:\n> ...\n>> I am perfectly aware that adding a \".github\" directory in the Git core\n>> tree is ugly. However, I believe the benefits (\"well informed new\n>> contributors\") outweigh the injury.\n\nI do not particulary see \".github\" as an injury, and we already\ncarry .travis.yml in our tree ;-)\n\nI agree with Ævar that mentioning the submitgit service would make\nthis even more helpful.\n"},{"id":"321867","messageId":"xmqqtw3o4nl8.fsf@gitster.mtv.corp.google.com","threadId":"46148","inReplyTo":"20170609170357.GE21733@aiede.mtv.corp.google.com","subject":"Re: [PATCH v1] Configure Git contribution guidelines for github.com","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2017-06-10T01:51:15Z","receivedAt":"2017-06-10T01:51:22Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Jonathan Nieder writes:\n\n> Lars Schneider wrote:\n>\n>> Many open source projects use github.com for their contribution process.\n>> Although we mirror the Git core repository to github.com [1] we do not\n>> use any other github.com service. This is unknown/unexpected to a\n>> number of (potential) contributors and consequently they create Pull\n>> Requests against our mirror with their contributions. These Pull\n>> Requests become stall [2]. This is frustrating to them as they think we\n>> ignore them and it is also unsatisfactory for us as we miss potential\n>> code improvements and/or new contributors.\n>\n> I think this description could be more focused. It's also not\n> self-contained --- e.g. the link to stalled pull requests is likely to\n> become stale over time, especially if GitHub gives us a way to disable\n> pull requests for the repository some day.\n>\n> Could you summarize for me the motivation behind this patch? Is it to\n> make Git more approachable, to avoid frustrating contributors, etc?\n\nI wonder if s/stall/stale/ is what Lars meant. I think it is fair\nto say that new contributors who are used to GitHub pull request\nwould find workflow with the mailing list unfamiliar, and from that\npoint of view, this is a step in a good direction. Back when I\nadded GitHub as one of the publishing repositories, the best way to\nconvey this message available to us was to have a short comment on\nthe repository telling the readers not to throw a pull-request at\nus. If there are other mechanisms to do so more effectively, we\nshould use it.\n"},{"id":"321892","messageId":"20170610073521.ewjzvtpha3xgoe6z@sigill.intra.peff.net","threadId":"46148","inReplyTo":"20170609170357.GE21733@aiede.mtv.corp.google.com","subject":"Re: [PATCH v1] Configure Git contribution guidelines for github.com","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2017-06-10T07:35:21Z","receivedAt":"2017-06-10T07:35:30Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Fri, Jun 09, 2017 at 10:03:57AM -0700, Jonathan Nieder wrote:\n\n> Would putting a PULL_REQUEST_TEMPLATE and CONTRIBUTING in the\n> top-level directory work? If I'm reading\n> https://help.github.com/articles/setting-guidelines-for-repository-contributors/#adding-a-contributing-file\n> correctly then it seems to say the \".github/\" prefix is optional.\n\nYes, that should work. The \".github\" option is there if you don't want\nthe cruft at your top-level. I don't mind CONTRIBUTING, but\nPULL_REQUEST_TEMPLATE is kind of gross. :)\n\n> I also find the long source lines hard to read. Can you say more\n> about how broken lines render in the github.com web interface? I\n> would have expected github's markdown renderer to behave like others\n> and cope with line wrapping.\n\nGitHub-Flavored Markdown treats newlines as a line break in the rendered\noutput, unlike the original Markdown implementation. I don't like that\nmyself, but it was done in the early days after seeing how many people\naccidentally butchered their formatting because they expected the output\nto look more like what they typed.\n\n-Peff\n"},{"id":"321917","messageId":"31A456B20D984421AA958A39B2FCD29D@PhilipOakley","threadId":"46148","inReplyTo":"20170609142151.94811-1-larsxschneider@gmail.com","subject":"Re: [PATCH v1] Configure Git contribution guidelines for github.com","fromName":"Philip Oakley","fromEmail":"philipoakley@iee.org","sentAt":"2017-06-10T12:48:50Z","receivedAt":"2017-06-10T12:48:58Z","isPatch":true,"sender":{"key":"philipoakley@iee.email","avatar":"https://avatars.githubusercontent.com/u/914343?v=4"},"body":"From: \"Lars Schneider\" \n> Many open source projects use github.com for their contribution process.\n> Although we mirror the Git core repository to github.com [1] we do not\n> use any other github.com service. This is unknown/unexpected to a\n> number of (potential) contributors and consequently they create Pull\n> Requests against our mirror with their contributions. These Pull\n> Requests become stall [2]. This is frustrating to them as they think we\n> ignore them and it is also unsatisfactory for us as we miss potential\n> code improvements and/or new contributors.\n>\n> GitHub offers a way to notify Pull Request contributors about the\n> contribution guidelines for a project [3]. Let's make use of this!\n>\n> [1] https://github.com/git/git\n> [2] https://github.com/git/git/pulls\n> [3] \n> https://help.github.com/articles/creating-a-pull-request-template-for-your-repository/\n>\n> Signed-off-by: Lars Schneider \n> ---\n\nI see there are currently 84 open PRs (13 in the last 14 days), so it is \nreal.\n\nI also see that the Issues page for git.git appears to be disabled, and will \nredirect to the pulls page.\n\nMaybe the instructions should also be part of an Issues template which could \nreduce the potential number of PRs being created (but could create its own \nproblems)\n\n\n>\n> Hi,\n>\n> I am perfectly aware that adding a \".github\" directory in the Git core\n> tree is ugly. However, I believe the benefits (\"well informed new\n> contributors\") outweigh the injury.\n>\n> You can see how a github.com Pull Request creation window would like here:\n> https://github.com/larsxschneider/git/compare/master...larsxschneider-patch-1?quick_pull=1\n>\n> I added a link that jumps to a part my GitMerge 2017 talk which explains\n> Git core contributions from my point view. Although I tried my best, the\n> presentation is not perfect and might not reflect the view of the Git\n> community. I wouldn't have a problem at all with removing the link.\n>\n> I also did not break the lines in the .github/*.md files as I thought it\n> renders nicer on the github.com web interface. I am happy to change that,\n> too, though.\n>\n> Cheers,\n> Lars\n>\n>\n> Notes:\n> Base Ref: master\n> Web-Diff: https://github.com/larsxschneider/git/commit/d859be5016\n> Checkout: git fetch https://github.com/larsxschneider/git \n> contrib-guide-v1 && git checkout d859be5016\n>\n> .github/CONTRIBUTING.md | 10 ++++++++++\n> .github/PULL_REQUEST_TEMPLATE.md | 3 +++\n> 2 files changed, 13 insertions(+)\n> create mode 100644 .github/CONTRIBUTING.md\n> create mode 100644 .github/PULL_REQUEST_TEMPLATE.md\n>\n> diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md\n> new file mode 100644\n> index 0000000000..8d01be6a71\n> --- /dev/null\n> +++ b/.github/CONTRIBUTING.md\n> @@ -0,0 +1,10 @@\n> +## Contributing to Git\n> +\n> +Thanks for taking the time to contribute to Git! Please be advised, that \n> the Git community does not use github.com for their contributions. \n> Instead, we use a [mailing list](http://public-inbox.org/git/) for code \n> submissions, code reviews, and bug reports.\n\nIsn't the mailing list git@vger.kernel.org, with an archive at \nhttp://public-inbox.org/git/ ?\n\n> +\n> +Please [read the maintainer \n> notes](http://repo.or.cz/w/git.git?a=blob_plain;f=MaintNotes;hb=todo) to \n> learn how the Git\n\nIs using the repo.or.cz address deliberate as a way of highlighting that \nGithub isn't the centre of the universe when accessing a DVCS repo?\n\nMaybe the kernel.org repo should be first, or at least the alt-git.git repo \nat repo.or.cz listed in those same notes.\n\n> +project is managed, and how you can work with it. In addition, we highly \n> recommend you to [read our submission \n> guidelines](../Documentation/SubmittingPatches).\n> +\n> +If you prefer video, then [this \n> talk](https://www.youtube.com/watch?v=Q7i_qQW__q4&feature=youtu.be&t=6m4s) \n> might be useful to you as the presenter walks you through the contribution \n> process by example.\n> +\n> +Your Git community\n> diff --git a/.github/PULL_REQUEST_TEMPLATE.md \n> b/.github/PULL_REQUEST_TEMPLATE.md\n> new file mode 100644\n> index 0000000000..c737a64620\n> --- /dev/null\n> +++ b/.github/PULL_REQUEST_TEMPLATE.md\n> @@ -0,0 +1,3 @@\n> +Thanks for taking the time to contribute to Git! Please be advised, that \n> the Git community does not use github.com for their contributions. \n> Instead, we use a mailing list for code submissions, code reviews, and bug \n> reports.\n> +\n> +Please read the \"guidelines for contributing\" linked above!\n>\n> base-commit: 8d1b10321b20bd2a73a5b561cfc3cf2e8051b70b\n> --\n> 2.13.0\n>\nIt's still a good idea though.\n--\nPhilip \n\n"},{"id":"321959","messageId":"xmqqlgoxp5ig.fsf@gitster.mtv.corp.google.com","threadId":"46148","inReplyTo":"31A456B20D984421AA958A39B2FCD29D@PhilipOakley","subject":"Re: [PATCH v1] Configure Git contribution guidelines for github.com","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2017-06-12T15:52:55Z","receivedAt":"2017-06-12T15:53:08Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"Philip Oakley\" writes:\n\n> From: \"Lars Schneider\" \n>> Many open source projects use github.com for their contribution process.\n>> Although we mirror the Git core repository to github.com [1] we do not\n>> use any other github.com service. This is unknown/unexpected to a\n>> number of (potential) contributors and consequently they create Pull\n>> Requests against our mirror with their contributions. These Pull\n>> Requests become stall [2]. This is frustrating to them as they think we\n>> ignore them and it is also unsatisfactory for us as we miss potential\n>> code improvements and/or new contributors.\n>>\n>> GitHub offers a way to notify Pull Request contributors about the\n>> contribution guidelines for a project [3]. Let's make use of this!\n>>\n>> [1] https://github.com/git/git\n>> [2] https://github.com/git/git/pulls\n>> [3]\n>> https://help.github.com/articles/creating-a-pull-request-template-for-your-repository/\n>>\n>> Signed-off-by: Lars Schneider \n>> ---\n>\n> I see there are currently 84 open PRs (13 in the last 14 days), so it\n> is real.\n\nNot so insignificant fraction of these are done purely for the\npurpose of using submitgit, though. In other words, if submitgit\nwere improved not to require a pull request against [1] (instead, it\ncould be pointed at a branch in a contributor's repository and do\nthe fromatting), these numbers will go down.\n\n>> +Thanks for taking the time to contribute to Git! Please be advised,\n>> that the Git community does not use github.com for their\n>> contributions. Instead, we use a [mailing\n>> list](http://public-inbox.org/git/) for code submissions, code\n>> reviews, and bug reports.\n>\n> Isn't the mailing list git@vger.kernel.org, with an archive at\n> http://public-inbox.org/git/ ?\n>\n\nI agree that I found the URL of the archive somewhat misleading for\nthose who want to contribute. Giving the mailing list address makes\na lot more sense. As suggested by Ævar in the thread, it would also\nbe good to suggest submitgit, given that the target audience of this\nmessage was already prepared to throw a pull request at us.\n\n>> +Please [read the maintainer\n>> notes](http://repo.or.cz/w/git.git?a=blob_plain;f=MaintNotes;hb=todo)\n>> to learn how the Git\n\nTwo minor issues here.\n\n1. push the \"read\" outside [], i.e.\n\n\tPlease read []() to learn...\n\n as what is inside [] and what is inside () ought to be the moral\n equivalents.\n\n2. the thing is not called \"the maintainer notes\"; it is called \"A\n note from the maintainer\". \n\n> Is using the repo.or.cz address deliberate as a way of highlighting\n> that Github isn't the centre of the universe when accessing a DVCS\n> repo?\n>\n> Maybe the kernel.org repo should be first, or at least the alt-git.git\n> repo at repo.or.cz listed in those same notes.\n\nI'd prefer [the k.org address](https://git.kernel.org/pub/scm/git/git.git/plain/MaintNotes?h=todo).\n\n>> +project is managed, and how you can work with it. In addition, we\n>> highly recommend you to [read our submission\n>> guidelines](../Documentation/SubmittingPatches).\n\nAgain, push \"read our\" outside [].\n\nThanks.\n"},{"id":"322055","messageId":"04B48EAE-E709-4A2A-A9C2-3473896B2F1E@gmail.com","threadId":"46148","inReplyTo":"xmqqlgoxp5ig.fsf@gitster.mtv.corp.google.com","subject":"Re: [PATCH v1] Configure Git contribution guidelines for github.com","fromName":"Lars Schneider","fromEmail":"larsxschneider@gmail.com","sentAt":"2017-06-13T07:45:32Z","receivedAt":"2017-06-13T07:45:41Z","isPatch":true,"sender":{"key":"larsxschneider@gmail.com","avatar":"https://avatars.githubusercontent.com/u/477434?v=4"},"body":"\n> On 12 Jun 2017, at 17:52, Junio C Hamano wrote:\n> \n> \"Philip Oakley\" writes:\n> \n>> From: \"Lars Schneider\" \n>>> Many open source projects use github.com for their contribution process.\n>>> Although we mirror the Git core repository to github.com [1] we do not\n>>> use any other github.com service. This is unknown/unexpected to a\n>>> number of (potential) contributors and consequently they create Pull\n>>> Requests against our mirror with their contributions. These Pull\n>>> Requests become stall [2]. This is frustrating to them as they think we\n>>> ignore them and it is also unsatisfactory for us as we miss potential\n>>> code improvements and/or new contributors.\n>>> \n>>> GitHub offers a way to notify Pull Request contributors about the\n>>> contribution guidelines for a project [3]. Let's make use of this!\n>>> \n>>> [1] https://github.com/git/git\n>>> [2] https://github.com/git/git/pulls\n>>> [3]\n>>> https://help.github.com/articles/creating-a-pull-request-template-for-your-repository/\n>>> \n>>> Signed-off-by: Lars Schneider \n>>> ---\n>> \n>> I see there are currently 84 open PRs (13 in the last 14 days), so it\n>> is real.\n> \n> Not so insignificant fraction of these are done purely for the\n> purpose of using submitgit, though. In other words, if submitgit\n> were improved not to require a pull request against [1] (instead, it\n> could be pointed at a branch in a contributor's repository and do\n> the fromatting), these numbers will go down.\n\nAs an alternative, could SubmitGit close the Pull Request automatically\nafter the mails have been send successfully?\n\n\n>>> +Thanks for taking the time to contribute to Git! Please be advised,\n>>> that the Git community does not use github.com for their\n>>> contributions. Instead, we use a [mailing\n>>> list](http://public-inbox.org/git/) for code submissions, code\n>>> reviews, and bug reports.\n>> \n>> Isn't the mailing list git@vger.kernel.org, with an archive at\n>> http://public-inbox.org/git/ ?\n>> \n> \n> I agree that I found the URL of the archive somewhat misleading for\n> those who want to contribute. Giving the mailing list address makes\n> a lot more sense. As suggested by Ævar in the thread, it would also\n> be good to suggest submitgit, given that the target audience of this\n> message was already prepared to throw a pull request at us.\n\nOK, will fix!\n\n\n>>> +Please [read the maintainer\n>>> notes](http://repo.or.cz/w/git.git?a=blob_plain;f=MaintNotes;hb=todo)\n>>> to learn how the Git\n> \n> Two minor issues here.\n> \n> 1. push the \"read\" outside [], i.e.\n> \n> \tPlease read []( \tthe thing>) to learn...\n> \n> as what is inside [] and what is inside () ought to be the moral\n> equivalents.\n> \n> 2. the thing is not called \"the maintainer notes\"; it is called \"A\n> note from the maintainer\". \n\nOK, will fix!\n\n\n>> Is using the repo.or.cz address deliberate as a way of highlighting\n>> that Github isn't the centre of the universe when accessing a DVCS\n>> repo?\n>> \n>> Maybe the kernel.org repo should be first, or at least the alt-git.git\n>> repo at repo.or.cz listed in those same notes.\n> \n> I'd prefer [the k.org address](https://git.kernel.org/pub/scm/git/git.git/plain/MaintNotes?h=todo).\n\nOK, will fix!\n\n\n> \n>>> +project is managed, and how you can work with it. In addition, we\n>>> highly recommend you to [read our submission\n>>> guidelines](../Documentation/SubmittingPatches).\n> \n> Again, push \"read our\" outside [].\n\nOK, will fix!\n\nThanks,\nLars"},{"id":"322056","messageId":"A712386E-0C4B-4A6C-B231-EA52FA285F34@gmail.com","threadId":"46148","inReplyTo":"31A456B20D984421AA958A39B2FCD29D@PhilipOakley","subject":"Re: [PATCH v1] Configure Git contribution guidelines for github.com","fromName":"Lars Schneider","fromEmail":"larsxschneider@gmail.com","sentAt":"2017-06-13T07:48:55Z","receivedAt":"2017-06-13T07:49:06Z","isPatch":true,"sender":{"key":"larsxschneider@gmail.com","avatar":"https://avatars.githubusercontent.com/u/477434?v=4"},"body":"\n> On 10 Jun 2017, at 14:48, Philip Oakley wrote:\n> \n> From: \"Lars Schneider\" \n>> Many open source projects use github.com for their contribution process.\n>> Although we mirror the Git core repository to github.com [1] we do not\n>> use any other github.com service. This is unknown/unexpected to a\n>> number of (potential) contributors and consequently they create Pull\n>> Requests against our mirror with their contributions. These Pull\n>> Requests become stall [2]. This is frustrating to them as they think we\n>> ignore them and it is also unsatisfactory for us as we miss potential\n>> code improvements and/or new contributors.\n>> \n>> GitHub offers a way to notify Pull Request contributors about the\n>> contribution guidelines for a project [3]. Let's make use of this!\n>> \n>> [1] https://github.com/git/git\n>> [2] https://github.com/git/git/pulls\n>> [3] https://help.github.com/articles/creating-a-pull-request-template-for-your-repository/\n>> \n>> Signed-off-by: Lars Schneider \n>> ---\n> \n> I see there are currently 84 open PRs (13 in the last 14 days), so it is real.\n> \n> I also see that the Issues page for git.git appears to be disabled, and will redirect to the pulls page.\n> \n> Maybe the instructions should also be part of an Issues template which could reduce the potential number of PRs being created (but could create its own problems)\n\nI don't think that is necessary as Issues are disabled for this repo.\n\n>> ...\n\n>> +Thanks for taking the time to contribute to Git! Please be advised, that the Git community does not use github.com for their contributions. Instead, we use a [mailing list](http://public-inbox.org/git/) for code submissions, code reviews, and bug reports.\n> \n> Isn't the mailing list git@vger.kernel.org, with an archive at http://public-inbox.org/git/ ?\n\nAgreed!\n\n> \n>> +\n>> +Please [read the maintainer notes](http://repo.or.cz/w/git.git?a=blob_plain;f=MaintNotes;hb=todo) to learn how the Git\n> \n> Is using the repo.or.cz address deliberate as a way of highlighting that Github isn't the centre of the universe when accessing a DVCS repo?\n\nHaha, partly yes. Plus, I wasn't able to figure out quickly how to access the todo blob on GitHub. \n\n\n> Maybe the kernel.org repo should be first, or at least the alt-git.git repo at repo.or.cz listed in those same notes.\n\nAgreed!\n\n\n> It's still a good idea though.\n\nThanks :)\n\n\n- Lars"},{"id":"322057","messageId":"DCA2782B-3439-4586-8105-170E47FA56C9@gmail.com","threadId":"46148","inReplyTo":"20170610073521.ewjzvtpha3xgoe6z@sigill.intra.peff.net","subject":"Re: [PATCH v1] Configure Git contribution guidelines for github.com","fromName":"Lars Schneider","fromEmail":"larsxschneider@gmail.com","sentAt":"2017-06-13T07:51:39Z","receivedAt":"2017-06-13T07:51:55Z","isPatch":true,"sender":{"key":"larsxschneider@gmail.com","avatar":"https://avatars.githubusercontent.com/u/477434?v=4"},"body":"\n> On 10 Jun 2017, at 09:35, Jeff King wrote:\n> \n> On Fri, Jun 09, 2017 at 10:03:57AM -0700, Jonathan Nieder wrote:\n> \n>> Would putting a PULL_REQUEST_TEMPLATE and CONTRIBUTING in the\n>> top-level directory work? If I'm reading\n>> https://help.github.com/articles/setting-guidelines-for-repository-contributors/#adding-a-contributing-file\n>> correctly then it seems to say the \".github/\" prefix is optional.\n> \n> Yes, that should work. The \".github\" option is there if you don't want\n> the cruft at your top-level. I don't mind CONTRIBUTING, but\n> PULL_REQUEST_TEMPLATE is kind of gross. :)\n\nI think so, too :)\n\n\n>> I also find the long source lines hard to read. Can you say more\n>> about how broken lines render in the github.com web interface? I\n>> would have expected github's markdown renderer to behave like others\n>> and cope with line wrapping.\n> \n> GitHub-Flavored Markdown treats newlines as a line break in the rendered\n> output, unlike the original Markdown implementation. I don't like that\n> myself, but it was done in the early days after seeing how many people\n> accidentally butchered their formatting because they expected the output\n> to look more like what they typed.\n\nThat's what I had in my memory based on past experience, too. However, \nout of curiosity I just tried it and it looks like they have changed it.\nI'll reformat with 80 chars.\n\n- Lars"},{"id":"322058","messageId":"C7CB1ED2-D7B0-40D3-A239-893BA444CF63@gmail.com","threadId":"46148","inReplyTo":"xmqqtw3o4nl8.fsf@gitster.mtv.corp.google.com","subject":"Re: [PATCH v1] Configure Git contribution guidelines for github.com","fromName":"Lars Schneider","fromEmail":"larsxschneider@gmail.com","sentAt":"2017-06-13T07:57:01Z","receivedAt":"2017-06-13T07:57:09Z","isPatch":true,"sender":{"key":"larsxschneider@gmail.com","avatar":"https://avatars.githubusercontent.com/u/477434?v=4"},"body":"\n> On 10 Jun 2017, at 03:51, Junio C Hamano wrote:\n> \n> Jonathan Nieder writes:\n> \n>> Lars Schneider wrote:\n>> \n>>> Many open source projects use github.com for their contribution process.\n>>> Although we mirror the Git core repository to github.com [1] we do not\n>>> use any other github.com service. This is unknown/unexpected to a\n>>> number of (potential) contributors and consequently they create Pull\n>>> Requests against our mirror with their contributions. These Pull\n>>> Requests become stall [2]. This is frustrating to them as they think we\n>>> ignore them and it is also unsatisfactory for us as we miss potential\n>>> code improvements and/or new contributors.\n>> \n>> I think this description could be more focused. It's also not\n>> self-contained --- e.g. the link to stalled pull requests is likely to\n>> become stale over time, especially if GitHub gives us a way to disable\n>> pull requests for the repository some day.\n>> \n>> Could you summarize for me the motivation behind this patch? Is it to\n>> make Git more approachable, to avoid frustrating contributors, etc?\n> \n> I wonder if s/stall/stale/ is what Lars meant.\n\nOf course :)\n\n- Lars\n"},{"id":"322298","messageId":"CACBZZX42JcqFAsWgi0bSuRv5CC8hiUF1Ahnx3nJL=LyHkk03Cg@mail.gmail.com","threadId":"46148","inReplyTo":"xmqqlgoxp5ig.fsf@gitster.mtv.corp.google.com","subject":"Re: [PATCH v1] Configure Git contribution guidelines for github.com","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2017-06-15T08:09:11Z","receivedAt":"2017-06-15T08:09:56Z","isPatch":true,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"On Mon, Jun 12, 2017 at 5:52 PM, Junio C Hamano wrote:\n> \"Philip Oakley\" writes:\n>\n>> From: \"Lars Schneider\" \n>>> Many open source projects use github.com for their contribution process.\n>>> Although we mirror the Git core repository to github.com [1] we do not\n>>> use any other github.com service. This is unknown/unexpected to a\n>>> number of (potential) contributors and consequently they create Pull\n>>> Requests against our mirror with their contributions. These Pull\n>>> Requests become stall [2]. This is frustrating to them as they think we\n>>> ignore them and it is also unsatisfactory for us as we miss potential\n>>> code improvements and/or new contributors.\n>>>\n>>> GitHub offers a way to notify Pull Request contributors about the\n>>> contribution guidelines for a project [3]. Let's make use of this!\n>>>\n>>> [1] https://github.com/git/git\n>>> [2] https://github.com/git/git/pulls\n>>> [3]\n>>> https://help.github.com/articles/creating-a-pull-request-template-for-your-repository/\n>>>\n>>> Signed-off-by: Lars Schneider \n>>> ---\n\n[The latest patch in this thread looks good to me to, thanks Lars]\n\n>> I see there are currently 84 open PRs (13 in the last 14 days), so it\n>> is real.\n>\n> Not so insignificant fraction of these are done purely for the\n> purpose of using submitgit, though. In other words, if submitgit\n> were improved not to require a pull request against [1] (instead, it\n> could be pointed at a branch in a contributor's repository and do\n> the fromatting), these numbers will go down.\n\nThere are things we get out of this that would regress if\nsubmitGit were changed this way:\n\n * Now when you submit a pull request you get a Travis build for\ngit/git, I don't get this if I push to any random branch in my\navar/git, and although I could probably set it up, it's extra work\netc.\n\n * I like being able to \"git fetch\" patches I'm reviewing. Now I can\njust set \"+refs/pull/*:refs/remotes/origin/pull/*\" in the refspec for\ngit/git, if it were pulling from target repos I'd need to \"git remote\nadd\" for each one, not a big deal, but less convenient.\n\n * There would be no single place to list submitGit requests, which\nyou can do now through the pull page, although I think this is largely\nstale now because nothing auto-closes them if they're merged (by which\npoint they'll have different sha1s), but that could be improved with\nsome bot...\n\nThere's probably ways to do this without git/git pull requests, but I\ndon't see what problem would be solved by moving this off git/git,\neven if there's open requests submitGit is the only thing using these,\nand any confusion about that pull UI would remain if it wasn't (AFAIK\nthere's no way to completely disable pull requests on github, but I\nmay be wrong).\n"},{"id":"322362","messageId":"xmqqk24d2oco.fsf@gitster.mtv.corp.google.com","threadId":"46148","inReplyTo":"CACBZZX42JcqFAsWgi0bSuRv5CC8hiUF1Ahnx3nJL=LyHkk03Cg@mail.gmail.com","subject":"Re: [PATCH v1] Configure Git contribution guidelines for github.com","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2017-06-15T16:43:35Z","receivedAt":"2017-06-15T16:43:54Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Ævar Arnfjörð Bjarmason writes:\n\n> There are things we get out of this that would regress if\n> submitGit were changed this way:\n>\n> * Now when you submit a pull request you get a Travis build for\n> git/git, I don't get this if I push to any random branch in my\n> avar/git, and although I could probably set it up, it's extra work\n> etc.\n\nThanks for pointing this out. I agree that this indeed is a\ndownside.\n\n> * I like being able to \"git fetch\" patches I'm reviewing. Now I can\n> just set \"+refs/pull/*:refs/remotes/origin/pull/*\" in the refspec for\n> git/git, if it were pulling from target repos I'd need to \"git remote\n> add\" for each one, not a big deal, but less convenient.\n>\n> * There would be no single place to list submitGit requests, which\n> you can do now through the pull page, although I think this is largely\n> stale now because nothing auto-closes them if they're merged (by which\n> point they'll have different sha1s), but that could be improved with\n> some bot...\n\nI do not think these two are 'regressions', unless your definition\nof 'regression' is a \"this thing I used to be able to do, now I no\nlonger can\", which is slightly different from mine, which is \"this\nuseful thing I used to be able to do, now I no longer can\".\n\nIt would be useful to be able to do the above two things, if the\nlist of submitGit requests and what you can get from pull/*\nhierarchy (1) covered most of the changes proposed, allowing people\nto check only this place and nowhere else, and/or (2) covered the\nmore interesting changes that are worth looking at than other\nproposed changes.\n\nI do not think either is the case. The submitGit mechanism being an\neasier way to propose a change to the mailing list, by definition,\n(1) will not hold true. And among the changes proposed to be made\nto Git, the \"selection criteria\" to be in the set to be discoverable\nby going to github.com/git/git.git and checking the submitGit pull\nrequests is not that they are of higher quality or touch interesting\ntopics. The only common trait these proposed changes share, compared\nto other proposed changes we see on the mailing list, are that they\nwere originally made as pull requests and (2) will not hold true.\n\nAnother thing that may regress that you did not mention is that we\nwould lose a convenient way to _count_ proposed changes coming via\nsubmitGit (i.e. you can simply go to the pull-request page), so that\nthe number can be compared with the number of proposed changes\ndirectly made on the mailing list, which would be a good way to\ngauge how submitGit service is helping our community. But even for\nthat, you'd need to go to the list to find the denominator\n(i.e. total number of changes proposed), and by the time you do\nthat, counting the numerator (i.e. those come via submitGit) by\nfinding the telltale sign submitGit leaves in its output among these\ndenominator messages should be trivial.\n\nSo in all, I see the only downside is the loss of automated\ntriggering of Travis. But I do agree with you that it is a rather\nsignificant downside.\n\n> There's probably ways to do this without git/git pull requests, but I\n> don't see what problem would be solved by moving this off git/git,\n> even if there's open requests submitGit is the only thing using these,\n> and any confusion about that pull UI would remain if it wasn't (AFAIK\n> there's no way to completely disable pull requests on github, but I\n> may be wrong).\n\nHopefully the pull-request template update Lars proposes will keep\nthe pull request useful, in that they create one and then have\nsubmitGit relay it to the official channel.\n"},{"id":"322366","messageId":"6e0de364-97a4-a2c1-eaea-8e9931cce6b5@gmail.com","threadId":"46148","inReplyTo":"xmqqk24d2oco.fsf@gitster.mtv.corp.google.com","subject":"Re: [PATCH v1] Configure Git contribution guidelines for github.com","fromName":"Andreas Heiduk","fromEmail":"asheiduk@gmail.com","sentAt":"2017-06-15T17:31:51Z","receivedAt":"2017-06-15T17:32:05Z","isPatch":true,"sender":{"key":"asheiduk@gmail.com","avatar":"https://avatars.githubusercontent.com/u/9371344?v=4"},"body":"Am 15.06.2017 um 18:43 schrieb Junio C Hamano:\n> Another thing that may regress that you did not mention is that we\n> would lose a convenient way to _count_ proposed changes coming via\n> submitGit (i.e. you can simply go to the pull-request page), so that\n> the number can be compared with the number of proposed changes\n> directly made on the mailing list, which would be a good way to\n> gauge how submitGit service is helping our community. But even for\n> that, you'd need to go to the list to find the denominator\n> (i.e. total number of changes proposed), and by the time you do\n> that, counting the numerator (i.e. those come via submitGit) by\n> finding the telltale sign submitGit leaves in its output among these\n> denominator messages should be trivial.\n\nThis numbers can be aquired quite easily if submitGit adds a defined\ntrailer to the converted commit message like this:\n\n\tSigned-off-by: Foo Bar \n\tSubmit-git-id: url-or-id-of-pr\n\n"},{"id":"322370","messageId":"xmqq37b12kuo.fsf@gitster.mtv.corp.google.com","threadId":"46148","inReplyTo":"6e0de364-97a4-a2c1-eaea-8e9931cce6b5@gmail.com","subject":"Re: [PATCH v1] Configure Git contribution guidelines for github.com","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2017-06-15T17:59:11Z","receivedAt":"2017-06-15T17:59:21Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Andreas Heiduk writes:\n\n> Am 15.06.2017 um 18:43 schrieb Junio C Hamano:\n>> Another thing that may regress that you did not mention is that we\n>> would lose a convenient way to _count_ proposed changes coming via\n>> submitGit (i.e. you can simply go to the pull-request page), so that\n>> the number can be compared with the number of proposed changes\n>> directly made on the mailing list, which would be a good way to\n>> gauge how submitGit service is helping our community. But even for\n>> that, you'd need to go to the list to find the denominator\n>> (i.e. total number of changes proposed), and by the time you do\n>> that, counting the numerator (i.e. those come via submitGit) by\n>> finding the telltale sign submitGit leaves in its output among these\n>> denominator messages should be trivial.\n>\n> This numbers can be aquired quite easily if submitGit adds a defined\n> trailer to the converted commit message like this:\n>\n> \tSigned-off-by: Foo Bar \n> \tSubmit-git-id: url-or-id-of-pr\n\nI do not think you would want the noise _in_ the log message. The\n\"telltale sign\" I had in mind was these \"signature\" lines at the end\nof the message:\n\n --\n https://github.com/git/git/pull/538\n\n"}]}