Recent commits to derivepassphrase.git (f7608463671f7220e5fc9c1585a3af94b1496390)

Fix multiple small issues with the CLI messages

2025-02-11T15:13:16+01:00

  * Otherwise empty translators comments were being prefixed with
    `TRANSLATORS:`, making them non-empty.

  * `Label.DERIVEPASSPHRASE_VAULT_NOTES_INSTRUCTION_TEXT` is actually
    pre-wrapped, but it was missing the "no wrap" marker.

  * In `ErrMsgTemplate.CANNOT_UPDATE_SETTINGS_NO_SETTINGS`, `--notes` is
    also a valid setting to specify.

  * The previous locale code `en_DEBUG` suggests that "DEBUG" is
    [a territory, not a modifier or variant][1].

[1]: https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap08.html
</pre>

Allow forcing the branch name on the automatic quality control script

2025-02-11T13:57:22+01:00

Allow forcing the branch name via the `GIT_CURRENT_BRANCH` environment
variable.  This is useful when the script doubles as a pre-commit hook,
and when we want to run the full set of checks normally reserved for
'master' only.
</pre>

Make the manpages installable under pipx

2025-02-11T00:57:53+01:00

When using `pipx` to install `derivepassphrase`, `pipx` will now
correctly locate the `derivepassphrase` manpages and make them available
to the user.
</pre>

Merge topic branch 'quality-control-automation' into master

2025-02-10T00:20:26+01:00

* t/quality-control-automation:
  Document the addition of quality control tools in the changelog
  Fix automatic quality control handling of too-long lines
  Fix minor message deviations in the source tree and phrasing in the manpages
  Add message IDs (and missing entries) to the manpage diagnostics listings
  Add quality control scripts
  Prepare `bump-my-version` for this project
  Store the version only in pyproject.toml
</pre>

Document the addition of quality control tools in the changelog

2025-02-10T00:15:57+01:00

</pre>

Fix automatic quality control handling of too-long lines

2025-02-09T22:17:47+01:00

In general, we want the formatter to deal with too-long lines (E501) as
much as possible by itself, and the linter to warn us on E501 lines the
formatter *cannot* deal with.  However, just naively running the linter
and formatter causes the linter to abort on any E501 lines it
encounters, because the linter cannot auto-fix them.  So we want to run
the linter twice, once before the formatter and once after the
formatter, while ignoring E501 violations in the first run.  (But
because E501 noqa markers are now treated as unnecessary noqa markers
during the first linting run, we actually need to ignore both E501 and
RUF100 in the first run.)
</pre>

Fix minor message deviations in the source tree and phrasing in the manpages

2025-02-09T20:58:40+01:00

</pre>

Add message IDs (and missing entries) to the manpage diagnostics listings

2025-02-09T20:47:17+01:00

Using the new quality control scripts, add message IDs to all diagnostic
messages described in the manpages, and add the entries missing from the
manpages as well.
</pre>

Add quality control scripts

2025-02-09T20:47:17+01:00

Add a quality control script `qc_auto.py` that calls the linter, the
formatter, the type checker, the test suite and the documentation
builder, depending on what branch we are on.  It is intended to be
usable as a pre-commit hook.

Add another quality control script `man_diagnostics.py` that checks that
the diagnostics documented in the manpages are complete, and match the
enum values within `derivepassphrase`.  It relies on annotations
(comments) in the manpages to map description texts to the respective
enum values (the mapping is not one-to-one).  It also does
a (rudimentary) check that every warning and error message is mentioned
somewhere in the source tree (besides the messages module that defines
those messages).
</pre>

Prepare `bump-my-version` for this project

2025-02-08T19:58:45+01:00

Prepare and configure the use of `bump-my-version` to automate keeping
version numbers synchronized everywhere.  From a cursory search, this
appears to be the most mature and actively developed tool of this kind
with support for `pyproject.toml` and multiple files with file-specific
replacements.  Some minor warts remain (non-recursive globbing,
duplication of the version number, incorrect calculation of the next
release due to missing true support for pre-release segments), but they
can be worked around, for now.
</pre>