Package to help you perform code reviews from your VC provider. Currently supports only Github.
Link to same PR on Github: wandersoncferreira/dotfiles#5
The Emacs everywhere goal continues. These are the main features of
code-review
to help you never leave Emacs to do Pull Request reviews.
- Start review from URL via
code-review-start
- Modern UI using magit-section and transient
- Read Pull Request comments
- Reply to comments
- Include code suggestions
- View
outdated
comments with the right diff hunk context - Approve, Reject or Request Changes for your PRs
- Integrated with
forge-topic-view
viacode-review-forge-pr-at-point
- Fast track commands like "LGTM! Approved"
- Review using single commits to focus on diff
- Set labels on RET. See details Multi value selection
- Set assignee. Use transient
sy
option toassign yourself
to the PR. - Set milestone. See details push access required
- Edit PR title
- Edit PR description body
- Merge your PR. (beta feature) See details merge
- Reactions. See details react to comments
- Save/Resume in-progress Reviews
The basic workflow:
RET
on a hunk diff line to add a commentRET
on a local comment to editRET
on a previous sent comment to include a replyC-c C-k
on a local comment to remove itr s f
to enable transient and Set a feedbackr a
to approve the PR |r r
to reject the PR |r c
to add comments in the PR
You can include your own bindings to functions like
code-review-comment-set-feedback
, code-review-approve
,
code-review-request-changes
, and code-review-comments
to not rely on the
transient panel. But I think you should see it :]
Missing something? Please, let us know.
I highly recommend installing code-review
through package.el
.
It's available on MELPA
.
M-x package-install code-review
Then you can either M-x code-review-start
and provide a PR URL or M-x code-review-forge-pr-at-point
if you are in a forge buffer over a PR.
Set code-review-fill-column
to define line wrap comment sections.
code-review
needs a GitHub token to act on your behalf for fetching PRs and
submitting reviews.
- Create a personal access token using GitHub
- Set the
repo
scope as the subscope of repo - If using GitHub enterprise / for business you also need the
write:discussion
read:discussion
scope.
Add a line to your auth source files with your login and token:
machine api.github.com login yourlogin^code-review password MYTOKENGOESHERE
You can access the transient panel by hitting r
from any place of the Code Review
buffer.
Binding | Object | Action |
---|---|---|
RET | hunk | Add Comment |
RET | comment | Add Reply |
RET | local comment (not sent to forge yet) | Edit local comment |
C-c C-k | local comment | Delete local comment |
C-c C-c | Comment Buffer | Register your local comment |
C-c C-k | Comment Buffer | Cancel your local comment |
C-c C-r | comment | Add Reaction |
C-c C-r | pr description | Add Reaction |
RET | reaction (on emoji symbol) | Endorse or Remove Reaction |
You can place code-review-forge-pr-at-point
to a key binding for your convenience:
(define-key forge-topic-mode-map (kbd "C-c r") 'code-review-forge-pr-at-point)
The package allows you to write integration with other forges to leverage these
functionalities. Take a look at code-review-core.el
to see which functions
need to be implemented.
Thanks Laurent Charignon for the awesome
github-review package and
stewardship. Github Review made me more familiar with the problem domain and
code-review
is an attempt to build on top of it.
Thanks Ag Ibragimov for the amazing idea to use
magit-section
to build a more suitable interface to this problem.