From: Brian Kubisiak <brian@kubisiak.com>
To: 55693@debbugs.gnu.org
Subject: [bug#55693] [PATCH v3 2/2] gnu: Add gitlint.
Date: Wed, 1 Jun 2022 18:56:46 -0700 [thread overview]
Message-ID: <20220602015646.gasbapfxxyrfa7yd@peregrine> (raw)
In-Reply-To: <20220528235330.hz2p6hsw5qcysaqc@peregrine>
* gnu/packages/version-control.scm (gitlint): New variable.
---
gnu/packages/version-control.scm | 37 ++++++++++++++++++++++++++++++++
1 file changed, 37 insertions(+)
diff --git a/gnu/packages/version-control.scm b/gnu/packages/version-control.scm
index 9d0786d2d9..e8a356df62 100644
--- a/gnu/packages/version-control.scm
+++ b/gnu/packages/version-control.scm
@@ -3371,3 +3371,40 @@ (define-public git-filter-repo
Git project instead of @command{git filter-branch}.")
(license (list license:expat ;; Main license.
license:gpl2)))) ;; For test harness.
+
+(define-public gitlint
+ (package
+ (name "gitlint")
+ (version "0.17.0")
+ (source (origin
+ (method url-fetch)
+ ;; the gitlint-core pypi package contains the actual gitlint
+ ;; code; the gitlint package only pulls in gitlint-core with
+ ;; stricter dependency versioning
+ (uri (pypi-uri "gitlint-core" version))
+ (sha256
+ (base32
+ "14cn89biys8r7mwcdgllv371k34km9k1941ylxf53a7sxwrzsbbp"))))
+ (build-system python-build-system)
+ (arguments
+ (list
+ #:phases
+ #~(modify-phases %standard-phases
+ (add-before 'build 'loosen-requirements
+ (lambda* (#:key inputs #:allow-other-keys)
+ (substitute* "gitlint/shell.py"
+ (("'git'") (string-append
+ "'"
+ (search-input-file inputs "bin/git")
+ "'"))
+ ;; force using subprocess instead of sh so git does not need
+ ;; to be a propagated input
+ (("if USE_SH_LIB") "if False")))))))
+ (inputs
+ (list git python-arrow python-click python-sh))
+ (home-page "https://jorisroovers.com/gitlint/")
+ (synopsis "Linting for your git commit messages")
+ (description
+ "Gitlint is a git commit message linter written in python: it checks your
+commit messages for style.")
+ (license license:expat)))
--
2.36.1
prev parent reply other threads:[~2022-06-02 2:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-28 23:53 [bug#55693] [PATCH 0/2] gnu: Add gitlint Brian Kubisiak
2022-05-28 23:55 ` [bug#55693] [PATCH 1/2] gnu: python-sh: Update to 1.14.2 Brian Kubisiak
2022-05-28 23:55 ` [bug#55693] [PATCH 2/2] gnu: Add gitlint Brian Kubisiak
2022-05-29 10:51 ` Maxime Devos
2022-05-29 21:37 ` Brian Kubisiak
2022-05-29 21:43 ` Maxime Devos
2022-05-30 23:17 ` [bug#55693] [PATCH v2 1/2] gnu: python-sh: Update to 1.14.2 Brian Kubisiak
2022-05-30 23:17 ` [bug#55693] [PATCH v2 2/2] gnu: Add gitlint Brian Kubisiak
2022-06-01 23:04 ` Maxime Devos
2022-06-05 21:19 ` [bug#55693] [PATCH 0/2] " Ludovic Courtès
2022-06-02 1:56 ` [bug#55693] [PATCH v3 1/2] gnu: python-sh: Update to 1.14.2 Brian Kubisiak
2022-06-05 21:25 ` bug#55693: [PATCH 0/2] gnu: Add gitlint Ludovic Courtès
2022-06-02 1:56 ` Brian Kubisiak [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: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220602015646.gasbapfxxyrfa7yd@peregrine \
--to=brian@kubisiak.com \
--cc=55693@debbugs.gnu.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://git.savannah.gnu.org/cgit/guix.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).