|
2 | 2 |
|
3 | 3 | This changelog does not follow semantic versioning. |
4 | 4 |
|
| 5 | +## 2.9.0 (26-Aug-2025) |
| 6 | + |
| 7 | +### Added |
| 8 | + |
| 9 | +- A `-S` / `--assignee` option has been added to the issues subcommand. |
| 10 | + This flag allows you to search for issues that are assigned to |
| 11 | + the given user. See the `gcli-issues(1)` manual page for more |
| 12 | + details. |
| 13 | + |
| 14 | +- An experimental `discussions` action was added to the pulls |
| 15 | + subcommand. It prints reviews and their comments in a threaded |
| 16 | + view. See the `gcli-pulls(1)` manual page for more details. |
| 17 | + |
| 18 | +- The online version of the gcli tutorial is now compiled into a |
| 19 | + manual page `gcli-tutorial(1)` which is installed by default. It |
| 20 | + is included pre-generated in the release tarball but can be rebuilt |
| 21 | + by setting the newly added `--enable-maintainer` option of the |
| 22 | + configure script. |
| 23 | + |
| 24 | +- Two actions `approve` and `unapprove` have been added to the |
| 25 | + `pulls` subcommand. These allow giving approval or rejecting a |
| 26 | + pull request, offering to enter a commant about why a given PR |
| 27 | + was approved or rejected. Because this reuses code from the |
| 28 | + reviews subsystem this currently only works on GitHub and Gitlab, |
| 29 | + however support for Gitea will be added in the next release. |
| 30 | + |
| 31 | +### Fixed |
| 32 | + |
| 33 | +- A bug in the autodetection of remotes and forge types from |
| 34 | + configured git remotes has been fixed. |
| 35 | + |
| 36 | + In cases where the git remote was pointing at an ssh-URL with a |
| 37 | + scheme but without a port the remote was not properly detected |
| 38 | + and lead to an incorrectly recognised owner/repo combination. |
| 39 | + |
| 40 | +- A confusion about the automerge feature has been fixed causing |
| 41 | + pull requests with automerge to not work on Github forges. Note |
| 42 | + that this does not fix the general bug on Github which doesn't |
| 43 | + correctly report whether a pull request has been marked as |
| 44 | + auto-merge. |
| 45 | + |
| 46 | +- Running the pulls checkout action as the last action used to |
| 47 | + result in an error 'not enough arguments'. |
| 48 | + |
| 49 | +### Changed |
| 50 | + |
| 51 | +- Compiler output file extensions are now guessed by the configure script |
| 52 | + |
| 53 | + This is done for Windows compatibility. People have reported that |
| 54 | + it is now possible again to build gcli on MSYS2. |
| 55 | + |
| 56 | + If the guessed extensions are wrong, one may override the guessed |
| 57 | + extensions using the environment variables `EXEEXT`, `OBJEXT`, |
| 58 | + `LIBEXT`, `EXEEXT_FOR_BUILD`, `OBJEXT_FOR_BUILD` and `LIBEXT_FOR_BUILD`. |
| 59 | + |
| 60 | +- When a pull/merge request or issue submission has failed, gcli |
| 61 | + will now store the entered message in `$PWD/gcli_message`. When |
| 62 | + the `pulls|issue create` subcommand is later re-run and this file |
| 63 | + is found, gcli will ask you whether you wish to recall its contents |
| 64 | + for the new message. |
| 65 | + |
| 66 | + Suggested-by: Bence Ferdinandy <bence@ferdinandy.com> |
| 67 | + |
| 68 | +- The pdjson dependency is now unbundled by default. In case it |
| 69 | + is not found via pkg-config the vendored copy is used instead. |
| 70 | + |
5 | 71 | ## 2.8.0 (25-May-2025) |
6 | 72 |
|
7 | 73 | ### Added |
|
0 commit comments