{"id":13861662,"url":"https://github.com/charignon/github-review","last_synced_at":"2026-01-17T00:57:53.066Z","repository":{"id":46619392,"uuid":"170053241","full_name":"charignon/github-review","owner":"charignon","description":"Github code reviews with Emacs.","archived":false,"fork":false,"pushed_at":"2021-10-29T02:43:48.000Z","size":520,"stargazers_count":313,"open_issues_count":23,"forks_count":24,"subscribers_count":11,"default_branch":"master","last_synced_at":"2024-08-05T06:03:32.330Z","etag":null,"topics":["code-review","emacs","emacs-lisp","github"],"latest_commit_sha":null,"homepage":"","language":"Emacs Lisp","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"gpl-3.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/charignon.png","metadata":{"files":{"readme":"README.md","changelog":"CHANGELOG.md","contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2019-02-11T02:12:24.000Z","updated_at":"2024-07-09T22:26:15.000Z","dependencies_parsed_at":"2022-09-01T21:02:07.659Z","dependency_job_id":null,"html_url":"https://github.com/charignon/github-review","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/charignon%2Fgithub-review","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/charignon%2Fgithub-review/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/charignon%2Fgithub-review/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/charignon%2Fgithub-review/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/charignon","download_url":"https://codeload.github.com/charignon/github-review/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":225968847,"owners_count":17553147,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["code-review","emacs","emacs-lisp","github"],"created_at":"2024-08-05T06:01:27.472Z","updated_at":"2026-01-17T00:57:53.049Z","avatar_url":"https://github.com/charignon.png","language":"Emacs Lisp","funding_links":[],"categories":["Emacs Lisp"],"sub_categories":[],"readme":"[![GPL v3](https://img.shields.io/badge/license-GPL_v3-green.svg)](http://www.gnu.org/licenses/gpl-3.0.txt)\n[![MELPA](https://melpa.org/packages/github-review-badge.svg)](https://melpa.org/#/github-review)\n\n# github-review: GitHub code reviews with Emacs.\n\nThis package contains a handful of Emacs commands to review GitHub pull request\nwithout leaving Emacs.\n\nTo get an overview of the package you can watch this 4-minute video:\n\n[![4-minute introduction](https://img.youtube.com/vi/u2tKzmKTNy4/0.jpg)](https://www.youtube.com/watch?v=u2tKzmKTNy4)\n\nYou can start by calling `github-review-start` and entering a Pull Request URL. You will, then be prompted with a buffer containing the diff of the pull request. The diff contains the description of the PR at the top with line starting with `~`. For example, reviewing [this pull request](https://github.com/clojure/clojurescript-site/pull/293) would open the following buffer:\n\n```diff\n~ Fix broken link to closure cheat sheet\n~\n~ The owner of http://www.closurecheatsheet.com/ lost the domain and does not intend to maintain it. This commit replaces the now defunkt link to http://www.closurecheat$\n~ ^M\n~ I also opened an issue on the cheat sheet repo to follow up with the author of the cheat sheet https://github.com/kuzmisin/closurecheatsheet/issues/12.\ndiff --git a/content/reference/google-closure-library.adoc b/content/reference/google-closure-library.adoc\nindex 58baa4b..eae7707 100644\n--- a/content/reference/google-closure-library.adoc\n+++ b/content/reference/google-closure-library.adoc\n@@ -18,7 +18,7 @@ rich-text editing, and UI widgets/controls.\n\n * http://google.github.io/closure-library/api/[Google Closure Library\n API Reference]\n-* http://www.closurecheatsheet.com/[Closure Cheatsheet] - abridged API\n+* https://github.com/kuzmisin/closurecheatsheet[Closure Cheatsheet] - abridged API\n with usage examples\n\n [[try-the-wrapper-libraries-first]]\n```\n\nYou can add comments at the top-level by writing lines starting with `#` after the PR description and before the beginning of the diff.\n\nYou can add comments inline by adding lines starting with `#` inline. See these features in the example below:\n\n```diff\n~ Fix broken link to closure cheat sheet\n~\n~ The owner of http://www.closurecheatsheet.com/ lost the domain and does not intend to maintain it. This commit replaces the now defunkt link to http://www.closurecheat$\n~ ^M\n~ I also opened an issue on the cheat sheet repo to follow up with the author of\nthe cheat sheet https://github.com/kuzmisin/closurecheatsheet/issues/12.\n# This is a global comment at the top of the file\n# with multiple\n# lines and will be submitted as a top level review comment\ndiff --git a/content/reference/google-closure-library.adoc b/content/reference/google-closure-library.adoc\nindex 58baa4b..eae7707 100644\n--- a/content/reference/google-closure-library.adoc\n+++ b/content/reference/google-closure-library.adoc\n@@ -18,7 +18,7 @@ rich-text editing, and UI widgets/controls.\n\n * http://google.github.io/closure-library/api/[Google Closure Library\n API Reference]\n-* http://www.closurecheatsheet.com/[Closure Cheatsheet] - abridged API\n+* https://github.com/kuzmisin/closurecheatsheet[Closure Cheatsheet] - abridged API\n# And a comment inline about\n# a specific line\n# ```with some\n# code```\n  with usage examples\n# Some other comment inline\n with usage examples\n\n [[try-the-wrapper-libraries-first]]\n```\n\nOnce done, you can submit your review with one of `github-review-approve`, `github-review-comment`, and `github-review-reject`.\n\n## Usage with Forge\n\nYou can use `github-review` with [`forge`](https://github.com/magit/forge).\nWhen your cursor is over a pull request, you can call `github-review-forge-pr-at-point` to start a code\nreview.\n\n## Installation\n\n### With melpa\n\nThis is the preferred way of installing this package.\n\n### With doom emacs\n\n`github-review` gets installed automatically if you are using the `magit` module.\n\nIf you just want to install `github-review` separately, add the following to your config:\n\n```emacs-lisp\n(package!\n github-review\n :recipe\n    (:host github\n     :repo \"charignon/github-review\"\n     :files (\"github-review.el\")))\n```\n\n## Configuration\n\n### GitHub\n\n`github-review` needs a GitHub token to act on your behalf for fetching PRs and\nsubmitting reviews.\n\n1. [Create a personal access token using GitHub](https://github.com/settings/tokens)\n2. Set the `repo` scope as the subscope of repo\n3. If using GitHub enterprise / for business you also need the `write:discussion` `read:discussion` scope.\n\n### Auth\nAdd a line to your auth source files with your login and token:\n\n```\nmachine api.github.com login yourlogin^github-review password MYTOKENGOESHERE\n```\n\n## Customization\n\nIf you use GitHub Enterprise, you can use the `github-review-host` custom variable to\nconfigure the endpoint of your GitHub Enterprise installation, this should look like `api.git.mycompany.com`.\n\n- By default, `github-review` fetches only top level comments in a pull request.\n  You can set `github-review-view-comments-in-code-lines` to `t` to also fetch\n  comments made between code lines.\n\n  You can also enable comments between code lines that are outdated by setting\n  `github-review-view-comments-in-code-lines-outdated` to `t`, however we cannot\n  guarantee correct placement of these comments in the review buffer.\n\n  You can also enable replies to inline comments by setting\n  `github-review-reply-inline-comments` to `t`, this feature only works if\n  `github-review-view-comments-in-code-lines` is also set to `t`. This way, if\n  you include a comment right after a previous received comment in the diff\n  buffer, your new comment will be sent as a reply.\n\n## Notice\n\n*I am providing code in the repository to you under an open source license. Because this is my personal repository, the license you receive to my\ncode is from me and not my employer (Facebook)*\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fcharignon%2Fgithub-review","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fcharignon%2Fgithub-review","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fcharignon%2Fgithub-review/lists"}