all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Vincent Legoll <vincent.legoll@gmail.com>,
	Arun Isaac <arunisaac@systemreboot.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Automatically checking commit messages
Date: Thu, 21 Sep 2017 20:59:12 +0200	[thread overview]
Message-ID: <87wp4ranen.fsf@fastmail.com> (raw)
In-Reply-To: <CAEwRq=r-S+ei1ZjAtNDVnwySkHmZkKwJUYki96HFn=gn-PaH5g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 924 bytes --]

Vincent Legoll <vincent.legoll@gmail.com> writes:

> Hello
>
> On Wed, Sep 20, 2017 at 5:47 PM, Arun Isaac <arunisaac@systemreboot.net> wrote:
>> I have been working on a guile script to automatically check commit
>> messages -- something like `guix lint' but for commit messages instead
>> of package definitions. This could help us enforce our commit message
>> guidelines and avoid screw-ups like the one I did in commit
>> 1ee879e96705e6381c056358b7f426f2cf99c1df. I believe more automation is
>> essential and would help us scale better if/when we have more people
>> with commit access.
>
> This is a good idea, and it would be even better if that same thing
> could be used to generate a commit message with all the automatable
> pieces pre-filled, with only the human parts left to the user.

FWIW 'magit' can already fill out file names and variables by navigating
to the hunks in the diff buffer and pressing 'C'.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

      reply	other threads:[~2017-09-21 18:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-20 15:47 Automatically checking commit messages Arun Isaac
2017-09-21 11:45 ` Jelle Licht
2017-09-23  4:44   ` Arun Isaac
2017-09-21 12:20 ` Vincent Legoll
2017-09-21 18:59   ` Marius Bakke [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wp4ranen.fsf@fastmail.com \
    --to=mbakke@fastmail.com \
    --cc=arunisaac@systemreboot.net \
    --cc=guix-devel@gnu.org \
    --cc=vincent.legoll@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.