From: Jeff King <peff@peff.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Roberto Tyley <roberto.tyley@gmail.com>
Subject: Re: [RFC/PATCH] point pull requesters to Git Git Gadget
Date: Fri, 15 Mar 2019 14:43:08 -0400 [thread overview]
Message-ID: <20190315184308.GC4941@sigill.intra.peff.net> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1903151427460.41@tvgsbejvaqbjf.bet>
On Fri, Mar 15, 2019 at 02:42:42PM +0100, Johannes Schindelin wrote:
> Another thing that I always dreamed of having: GitGitGadget could
> automatically warn about commit messages that are incomplete, that
> disagree with our preferred format, that contain typos or offensive
> language.
>
> Likewise, I had this idea that once we had some robust Clang format
> definition, GitGitGadget could verify that the patches conform to what we
> want, and automatically generate fixed branches if not.
>
> Basically, all the automation I can get, to relieve humans from tasks that
> machines can do.
>
> Children can have dreams, can't they ;-)
I like all of those dreams. :)
I think the "checks" could all just be another form of CI. I think there
may be some tricks with automatic rewriting, but it might be possible to
do it in the form of GitHub "suggestions", which a human could then
click "OK" to a bunch of them. I guess it would be overwhelming if you
really diverged style-wise and the diff is large.
I don't think GitHub has any support for changing commit messages,
though, short of your tool force-pushing.
-Peff
next prev parent reply other threads:[~2019-03-15 18:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 21:32 [RFC/PATCH] point pull requesters to Git Git Gadget Jeff King
2019-03-12 23:08 ` Roberto Tyley
2019-03-13 19:34 ` Jeff King
2019-03-13 20:50 ` Johannes Schindelin
2019-03-13 1:49 ` Junio C Hamano
2019-03-13 19:39 ` Jeff King
2019-03-13 20:18 ` Jeff King
2019-03-14 11:31 ` Johannes Schindelin
2019-03-15 3:19 ` Jeff King
2019-03-15 13:42 ` Johannes Schindelin
2019-03-15 18:43 ` Jeff King [this message]
2019-03-18 2:52 ` Junio C Hamano
2019-03-18 21:12 ` Jeff King
2019-03-18 21:48 ` Thomas Gummerer
2019-03-18 21:52 ` Jeff King
2019-03-19 0:30 ` Junio C Hamano
2019-03-18 22:25 ` Ævar Arnfjörð Bjarmason
2019-03-13 21:05 ` Johannes Schindelin
2019-03-13 22:17 ` Junio C Hamano
2019-03-13 2:07 ` Junio C Hamano
2019-03-13 2:18 ` Junio C Hamano
2019-03-13 19:39 ` Jeff King
2019-03-14 12:04 ` GitGitGadget on github.com/git/git?, was " Johannes Schindelin
2019-03-14 14:46 ` Duy Nguyen
2019-03-15 3:30 ` Jeff King
2019-03-15 14:51 ` Johannes Schindelin
2019-03-15 16:28 ` Ævar Arnfjörð Bjarmason
2019-03-15 18:41 ` Jeff King
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190315184308.GC4941@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=roberto.tyley@gmail.com \
/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.
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 NNTP newsgroup(s).