2.5.0

I am pleased to announce the release of gcli 2.5.0!
Included are lots of bug fixes and a few new improvements such as optional support for lowdown to render markdown.

Thank you for all the contributions and bug reports.

You can find a summary of all the changes below.

Please report back in case you find bugs, bad documentation or other suggestions you have.
You can reach us on IRC in #gcli on Libara.Chat or on the mailing list at https://lists.sr.ht/~herrhotzenplotz/gcli-discuss.

Download

You can find release tarballs here:

https://herrhotzenplotz.de/gcli/releases/gcli-2.5.0/

Changelog

Added

• Added a -R flag to the comment subcommand that allows you to
  reply to a comment with the given ID.

Fixed

• In various configuration places and environment variables where
  boolean values are accepted you can now specify true as a truthy
  value.

  Submitted by: Gavin-John Noonan [email protected]

• The configure script now exits gracefully whenever a required
  program couldn't be found.

  Reported by: Alexey Ugnichev [email protected]

• A bug genereting invalid JSON when adding labels to a GitHub issue
  was fixed.

• The reviews cache directory is now automatically created if it
  doesn't exist avoiding a 'No such file or directory' error when
  invoking the review action for the first time.

  Reported by: Bence Ferdinandy [email protected]

• A few bugs in the patch parser have been fixed:

  • Under rare conditions hunk ranges were incorrectly parsed
  • Parser errors when a diff included lines starting with a backslash
    (e.g. when there is no newline at the end of file) were fixed

  Reported by: Bence Ferdinandy [email protected]

• The installation location of the manual pages of gcli has been
  fixed. The latest release accidentially installed manual pages to
  ${DESTDIR}${PREFIX}/share/man instead of
  ${DESTDIR}${PREFIX}/share/man/manX.

  Reported by: Bence Ferdinandy [email protected]

Changed

• The pipelines subcommand has been refactored to accept actions
  for pipelines. This allows cases where a pipeline triggers child
  pipelines to be handled properly.

  See gcli-pipelines(1) for documentation.

  Reported by: Bence Ferdinandy [email protected]