Tags give the ability to mark specific points in history as being important
-
v2.13.0
Release: Version 2.13.07a94c96f · ·Version 2.13.0 Changelog ========= Fixed ~~~~~ - Parsing of integer arguments on the CLI have been fixed Specifically, this concerns the following edge cases where: - `-n <count>` was truncated due to conversion to long integers - `-i <id>` caused an arithmetic overflow due to converting a negative integer to an unsigned integer This only occured when the user provided such illegal values and thus caused the bug. Reported-by: Sulev-Madis Silber - A crash that occured when trying to print a non-existant Bugzilla attachment has been fixed Reported-by: Sulev-Madis Silber - The manual page `gcli-status(1)` has been fixed and was updated to reflect the current behaviour - A crash when creating a repo on GitHub without specifying a description has been fixed. Reported-by: Sandro Santilli - Modifying labels attached to issues and pull requests on Gitea has been fixed Previously this silently failed. Reported-by: Michael Niedermayer Added ~~~~~ - The `attachments` subcommand gained support for creating Bugzilla attachments as well as marking them as obsolete - A new manual page `gcli-attachments(1)` has been added documenting the options of this subcommand. The `gcli(1)` manual page has been updated and references the new manual page as well. - It is now possible to search for repositories via the `gcli repos` subcommand. Search keywords are taken as is after the subcommand: gcli repos foo bar baz This would search for `foo bar baz`. Suggested by: Dmitry Atamanov <https://github.com/data-man> Changed ~~~~~~~ - `gcli labels` now includes inherited labels from the organisation for Gitea - When performing actions on a repository via `gcli repos` it is now mandatory to specify both the owner and the repository name via `-o` and `-r` respectively. -
v2.12.0
Release: Version 2.12.0274867e7 · ·Version 2.12.0 Fixed ~~~~~ - issue_set_milestone has been fixed for GitLab This unbreaks the `milestone` action in the issues subcommand for GitLab. Previous versions of gcli have incorrectly generated the request URL to the GitLab API resulting in cryptic error messages. Added ~~~~~ - Subcommands now accept an optional `forge:owner/repo` positional argument As a shorthand for `-t github -o torvalds -r linux`, you can write: ``` gcli issues gh:curl/curl gcli pulls gl:gitlab-org/gitlab gcli pipelines cb:forgejo/forgejo ``` The built-in prefixes are `gh:` (GitHub), `gl:` (GitLab), and `cb:` (Codeberg). Named account sections from the gcli config file are also accepted as the prefix. For example, given: ``` freebsd-bz { apibase=https://bugs.freebsd.org/bugzilla forge-type=bugzilla } work-gl { apibase=https://gitlab.example.com forge-type=gitlab } ``` These work as positional arguments: ``` gcli issues freebsd-bz:"Base System/tests" gcli pulls work-glb:acme-corp/frontend ``` Note: for Bugzilla the path is `product/component` rather than `owner/repo`. This works across all repository subcommands: `issues`, `pulls`, `pipelines`, `ci`, `releases`, `forks`, `labels`, `milestones`, and `comment`. The existing `-t`, `-o`, and `-r` flags remain supported. Changed ~~~~~~~ - The pipelines subcommand now supports GitHub actions The old ci subcommand that was undocumented and not well maintained has been removed. The pipeline subcommand now additionally gained a `monitor` action that allows continuous monitoring of a running CI check suite / pipeline. This new action requires an Xterm-compatible terminal emulator to function correctly. Suggested by: Sergey Bronnikov <https://github.com/ligurio> Removed ~~~~~~~ - The `ci` subcommand has been removed because it was undocumented and not well maintained. -
v2.11.0
Release: Version 2.11.0b7c1f49d · ·Release version 2.11.0 - The git config parser has been made more robust It has been rewritten as a proper parser which has dedicated unit tests - The setting `restrict-pipelines-to-branch = yes` in the `defaults` section of the gcli config file allows you to make the `gcli pipelines` subcommand only list GitLab pipelines running on the currently checked out branch by default. For listing pipelines running on any ref, a `-a` flag has been added. This setting is turned off by default in order not to break the existing behaviour. Please speak up if you wish to have this be the default or not. See also: `gcli-pipelines(1)` - GCLI now tries to infer most of the interactive prompt questions for branches and remotes from the VCS in use This specifically applies to: - Source branch and owner, by looking at the current branch, finding its tracking remote and using its owner - Target branch, by looking at the owner/repo of the MR/PR target and using the matching remote's HEAD (which typically points at a branch) Suggested-by: 999faryad <https://github.com/999faryad> - GCLI's manual pages are now installed gzip compressed by default -
v2.9.1
Release: Version 2.9.1e6c678fe · ·Version 2.9.1 Only a fix for the double free that had been lurking in here for a while.
-
-
-
-
-