Skip to content

2.8.0

Latest
Latest
Compare
Choose a tag to compare
@herrhotzenplotz herrhotzenplotz released this 25 May 15:42
v2.8.0
f8f7bcf
This commit was signed with the committer’s verified signature.
herrhotzenplotz Nico Sonack
GPG key ID: F373F52545A28D14
Verified
Learn about vigilant mode.

I am pleased to announce version 2.8.0 of gcli after two months of mostly silence.

Below you can find the changelog for this version.

Tarballs can be downloaded from https://herrhotzenplotz.de/gcli/releases/gcli-2.8.0/.

Please note that I do not support the auto-generated release tarballs from GitHub and Gitlab.

A big thank you for all the bug reports and suggestions!

Please test and report bugs!
If you package for a new operating system please let me know!

Contact

Changelog

Added

  • The pulls subcommand now supports assigning pull requests to users.
    A new assign action has been added.

  • The releases create subcommand now has an option -T/--template.
    This option allows you to pass a path to a file that is used for the release notes.
    If combined with --yes the entire command is non-interactive allowing you to use it from scripts.
    If not combined with --yes an editor is opened with a copy of the passed file, allowing you to use it as a template for further editing.

    See the manual page gcli-releases(1) for details and usage examples.

    Suggested by: xaizek https://github.com/xaizek

Fixed

  • Parsing timestamps with timezone offsets now works properly.
    This was an issue on Gitea forges where sometimes timestamps with explicit timezone offsets were returned.

  • Building on macOS has been fixed

    Darwin doesn't have a separate library for the POSIX real-time extensions.
    Trying to link with -lrt thus results in errors.

    The configure script now explicitly checks for a host platform apple-darwin and disables -lrt linkage in this case.

    Reported by: botantony https://gitlab.com/botantony

  • Fixed a crash in jemalloc caused by a double-free in the patch action on Gitlab

    This only occured in the case where multiple patches are in a merge request.

  • Fixed incorrect argument parsing in the pipelines subcommand leading to a nonsensical error message

  • Fixed broken automerge feature when creating merge requests on Gitlab.

Future directions

  • I am planning to rewrite the review code as it is currently in a unusable state.
    This is also the reason why it has been marked as experimental for a while now.
Assets 2
Loading