From: Jonathan Nieder <jrnieder@gmail.com>
To: Lars Schneider <larsxschneider@gmail.com>
Cc: git@vger.kernel.org, gitster@pobox.com, philipoakley@iee.org,
avarab@gmail.com, peff@peff.net
Subject: Re: [PATCH v3] Configure Git contribution guidelines for github.com
Date: Wed, 14 Jun 2017 10:46:47 -0700 [thread overview]
Message-ID: <20170614174647.GV133952@aiede.mtv.corp.google.com> (raw)
In-Reply-To: <20170614073536.45498-1-larsxschneider@gmail.com>
Lars Schneider wrote:
> Many open source projects use github.com for their contribution process.
> Although we mirror the Git core repository to github.com [1] we do not
> use any other github.com service. This is unknown/unexpected to a
> number of (potential) contributors and consequently they create Pull
> Requests against our mirror with their contributions. These Pull
> Requests become stale. This is frustrating to them as they think we
> ignore them and it is also unsatisfactory for us as we miss potential
> code improvements and/or new contributors.
>
> GitHub contribution guidelines and a GitHub Pull Request template that
> is visible to every Pull Request creator can be configured with special
> files in a Git repository [2]. Let's make use of this!
>
> [1] https://github.com/git/git
> [2] https://help.github.com/articles/creating-a-pull-request-template-for-your-repository/
>
> Signed-off-by: Lars Schneider <larsxschneider@gmail.com>
> ---
> .github/CONTRIBUTING.md | 19 +++++++++++++++++++
> .github/PULL_REQUEST_TEMPLATE.md | 7 +++++++
> 2 files changed, 26 insertions(+)
> create mode 100644 .github/CONTRIBUTING.md
> create mode 100644 .github/PULL_REQUEST_TEMPLATE.md
Reviewed-by: Jonathan Nieder <jrnieder@gmail.com>
Thanks.
prev parent reply other threads:[~2017-06-14 17:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 7:35 [PATCH v3] Configure Git contribution guidelines for github.com Lars Schneider
2017-06-14 7:37 ` Jeff King
2017-06-14 17:46 ` Jonathan Nieder [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170614174647.GV133952@aiede.mtv.corp.google.com \
--to=jrnieder@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=larsxschneider@gmail.com \
--cc=peff@peff.net \
--cc=philipoakley@iee.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).