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.