![]() |
![]()
| ![]() |
![]()
NAME
SYNOPSIS
DESCRIPTIONWARNING!
This feature is rather new. Expect bugs and broken features. Please report
bugs if you hit any. The same also applies to this manual page. Please
suggest improvements that can be made to this feature too. To enable this
experimental action you must either set “enable-experimental”
in your gcli config file (see
gcli(5))
to “yes” or set the environment variable
The Running this action will drop you into your editor and lets you annotate the diff of the PR. Comments are always above the change they refer to. A change is either a single diff line or multiple lines wrapped in curly braces on the lines surrounding the change. Comments may be prefixed with “>”: @@ foo.md -0,0 +0,0 @@ hunk starts here No change This is a single line comment +Foo > This is is a multiline comment on a multiline diff. > > Comment continues here. { not a change -Removed this line +Added this line +Added another line. } this is also not a change The above example produces two comments, the first referring only to the addition of “Foo” and the second referring to 4 lines surrounded by the curly braces. Everything leading up to the first diff will be attached as a top-level comment for your review. After you saved and exited the editor you will be asked what actions to take on your review. This allows you to request changes, approve the changes, leave a plain comment or to postpone the review locally. OPTIONSEXAMPLESReview PR #69 in the current inferred forge and remote: $ gcli pulls -i 69 review Review PR #12 in curl/curl on Github: $ gcli -t github pulls -o curl -r curl -i 12 review SEE ALSOAUTHORSNico Sonack aka. herrhotzenplotz <nsonack@herrhotzenplotz.de> and contributors. BUGSAt the moment the diff cache directory is not created automagically. You have to manually create it in case gcli complains. This feature is not implemented (but in active development) on Gitea. Please report bugs at https://sr.ht/~herrhotzenplotz/gcli, via E-Mail to https://lists.sr.ht/~herrhotzenplotz/gcli-discuss or on Github.
|