From: Patrick Steinhardt <ps@pks.im>
To: git@vger.kernel.org
Subject: [PATCH 0/4] Documentation: improve linting of manpage existence
Date: Wed, 5 Jun 2024 07:16:42 +0200 [thread overview]
Message-ID: <cover.1717564310.git.ps@pks.im> (raw)
[-- Attachment #1: Type: text/plain, Size: 1270 bytes --]
Hi,
in [1], Junio noticed that `make check-docs` was failing for a recent
patch series of mine that introduces the new git-refs(1) command.
Curiously though, while the checks do print errors, the Makefile target
itself succeeded and thus did not make the corresponding CI job fail.
This patch series fixes that issue and also refactors the infrastructure
such that it fits better into our existing set of linter targets for our
documentation. Finally, this series then adds a job to GitLab CI that is
equivalent to the job we already have on GitHub Actions.
[1]: <xmqqjzj9czop.fsf@gitster.g>
Patrick
Patrick Steinhardt (4):
Makefile: extract script to lint missing/extraneous manpages
Documentation/lint-manpages: bubble up errors
gitlab-ci: add job to run `make check-docs`
ci/test-documentation: work around SyntaxWarning in Python 3.12
.gitlab-ci.yml | 9 +++
Documentation/Makefile | 4 ++
Documentation/lint-manpages.sh | 107 +++++++++++++++++++++++++++++++++
Makefile | 36 -----------
ci/test-documentation.sh | 1 +
5 files changed, 121 insertions(+), 36 deletions(-)
create mode 100755 Documentation/lint-manpages.sh
--
2.45.2.409.g7b0defb391.dirty
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2024-06-05 5:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 5:16 Patrick Steinhardt [this message]
2024-06-05 5:16 ` [PATCH 1/4] Makefile: extract script to lint missing/extraneous manpages Patrick Steinhardt
2024-06-05 5:20 ` Junio C Hamano
2024-06-05 5:27 ` Patrick Steinhardt
2024-06-06 6:03 ` James Liu
2024-06-06 6:12 ` Junio C Hamano
2024-06-05 5:16 ` [PATCH 2/4] Documentation/lint-manpages: bubble up errors Patrick Steinhardt
2024-06-05 5:22 ` Junio C Hamano
2024-06-05 5:16 ` [PATCH 3/4] gitlab-ci: add job to run `make check-docs` Patrick Steinhardt
2024-06-05 5:17 ` [PATCH 4/4] ci/test-documentation: work around SyntaxWarning in Python 3.12 Patrick Steinhardt
2024-06-05 5:24 ` Junio C Hamano
2024-06-06 8:00 ` [PATCH v2 0/4] Documentation: improve linting for manpage existence Patrick Steinhardt
2024-06-06 8:01 ` [PATCH v2 1/4] Makefile: extract script to lint missing/extraneous manpages Patrick Steinhardt
2024-06-07 16:51 ` Junio C Hamano
2024-06-06 8:01 ` [PATCH v2 2/4] Documentation/lint-manpages: bubble up errors Patrick Steinhardt
2024-06-06 8:01 ` [PATCH v2 3/4] gitlab-ci: add job to run `make check-docs` Patrick Steinhardt
2024-06-06 8:01 ` [PATCH v2 4/4] ci/test-documentation: work around SyntaxWarning in Python 3.12 Patrick Steinhardt
2024-06-07 0:59 ` [PATCH v2 0/4] Documentation: improve linting for manpage existence James Liu
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=cover.1717564310.git.ps@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.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.
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).