From: Jim Porter <jporterbugs@gmail.com>
To: Po Lu <luangruo@yahoo.com>, Stefan Kangas <stefankangas@gmail.com>
Cc: No Wayman <iarchivedmywholelife@gmail.com>, 68691@debbugs.gnu.org
Subject: bug#68691: 30.0.50; [WISHLIST] Make it easier to conform to desired commit message format
Date: Fri, 26 Jan 2024 10:44:31 -0800 [thread overview]
Message-ID: <0bc92736-be1d-f5da-645b-56edf4af193f@gmail.com> (raw)
In-Reply-To: <87il3gopdq.fsf@yahoo.com>
On 1/25/2024 5:27 PM, Po Lu via Bug reports for GNU Emacs, the Swiss
army knife of text editors wrote:
> A hook run before each commit is a good idea, and I plan to study how
> they are written.
We already have a few hooks for this, including a `commit-msg` hook that
checks for various formatting issues, and `post-commit` + `pre-push`
hooks to verify that the files listed in the message match the diff.
(There are some annoying technical reasons for using `post-commit` and
`pre-push` for this, which are documented in their implementations under
build-aux/git-hooks/.)
You could probably consult the existing implementations to see how to do
things, and improve them with any extra features that might help here.
next prev parent reply other threads:[~2024-01-26 18:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 17:20 bug#68691: 30.0.50; [WISHLIST] Make it easier to conform to desired commit message format No Wayman
2024-01-25 23:09 ` Stefan Kangas
2024-01-26 1:27 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-26 18:44 ` Jim Porter [this message]
2024-01-28 0:44 ` Stefan Kangas
2024-01-28 6:18 ` Eli Zaretskii
2024-01-28 7:21 ` Stefan Kangas
2024-01-28 7:33 ` Eli Zaretskii
2024-01-28 8:43 ` Juri Linkov
2024-01-26 7:18 ` Eli Zaretskii
2024-01-28 1:07 ` Stefan Kangas
2024-01-28 6:21 ` Eli Zaretskii
2024-01-28 7:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-28 7:42 ` Eli Zaretskii
2024-01-28 9:04 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-28 9:57 ` Eli Zaretskii
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=0bc92736-be1d-f5da-645b-56edf4af193f@gmail.com \
--to=jporterbugs@gmail.com \
--cc=68691@debbugs.gnu.org \
--cc=iarchivedmywholelife@gmail.com \
--cc=luangruo@yahoo.com \
--cc=stefankangas@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/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.