code-review
Code Reviews in Emacs (by wandersoncferreira)
gh-notify
Veneer for the Magit/Forge GitHub porcelain (by anticomputer)
| code-review | gh-notify | |
|---|---|---|
| 15 | 6 | |
| 448 | 68 | |
| - | - | |
| 0.0 | 5.4 | |
| 6 months ago | 25 days ago | |
| Emacs Lisp | Emacs Lisp | |
| GNU General Public License v3.0 only | BSD 2-clause "Simplified" License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
code-review
Posts with mentions or reviews of code-review.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-29.
-
Is orgmode really that much better than an equivalent workflow using vim + other tools?
Besides all that, I'm also having to take care of my work duties. When I started my day earlier, as per usual, I opened gh-notify buffer to check all GitHub notifications. Issues, Pull-requests. Using code-review I quickly checked a few PRs, scrolled through the diffs, posted a couple of comments, and approved the PRs.
-
Perfect workflow with Emacs, Org and Cron
If I want to review a PR, there's code-review.
-
Can you settle this for me once and for all? What can emacs do that neovim+plugins can't?
Hit Ctrl-p from comment up into diff in code-review, hit RET to go directly to real file in correct place (feature not yet implemented)
-
GitHub and Doom Emacs
The second problem is reviewing PRs. The best Emacs package for that today is code-review.el. I briefly talked about it a while ago https://twitter.com/iLemming/status/1463317344437121025
- [v0.0.6] Code review release - Bitbucket Cloud support finally here!
-
Support to code review Bitbucket Cloud PRs
Happy to say that my initial goal to support Github, Gitlab & Bitbucket is finally coming together. This PR https://github.com/wandersoncferreira/code-review/pull/156 includes basic bitbucket review workflow to the package.
- [v0.0.5] Code Review package
-
[v0.0.4] Code Review package
As long as there are only two contributors (of which only one has signfiicant contributions), why not add it to ELPA? If the author reads this and is interested, send an email to emacs-devel.
- [v0.0.3] Code Review package
-
Reply to comments in code review using wandersoncferreira/code-review
I'm trying to use wandersoncferreira/code-review to do GitHub code reviews from Emacs. As a review author, I'd like to reply to comments reviewers have made. If I on such a comment in the *Code Review* buffer, I get a new buffer where I can write my own comment. I do C-c C-c when I'm done. My comments then shows up in the *Code Review* buffer. But how do I submit my comments to GitHub. I have tried a number of M-x calls but non of them is working for me. How do I submit my comment replies? I really like the package by the way, It's great to be able to do code reviews from inside Emacs.
gh-notify
Posts with mentions or reviews of gh-notify.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-07-04.
-
Managing email with Notmuch and Emacs
I highly recommend anticomputer/gh-notify for that.
-
Is orgmode really that much better than an equivalent workflow using vim + other tools?
Besides all that, I'm also having to take care of my work duties. When I started my day earlier, as per usual, I opened gh-notify buffer to check all GitHub notifications. Issues, Pull-requests. Using code-review I quickly checked a few PRs, scrolled through the diffs, posted a couple of comments, and approved the PRs.
-
GitHub and Doom Emacs
The third thing is GitHub notifications. I don't know about you, but I have to deal with hundreds of them every day. Not kidding at all. That becomes really difficult because GitHub's notifications interface ain't built for efficiency. You need to check gh-notify.el
- Elisp Struct's read-only slot dilemma
- gh-notify: A thin ui veneer on top of Magit/Forge porcelain for juggling large amounts of GitHub notifications at speed.
- gh-notify: a Magit/Forge veneer
What are some alternatives?
When comparing code-review and gh-notify you can also consider the following projects:
magit - It's Magit! A Git Porcelain inside Emacs.
gist.el - Yet another Emacs paste mode, this one for Gist.
lieer - Fast email-fetching and sending and two-way tag synchronization between notmuch and GMail
toc-org - toc-org is an Emacs utility to have an up-to-date table of contents in the org files without exporting (useful primarily for readme files on GitHub)
evil - The extensible vi layer for Emacs.
github-review - Github code reviews with Emacs.
jist.el - Yet another gist client for Emacs
neogit - An interactive and powerful Git interface for Neovim, inspired by Magit
org-noter - Emacs document annotator, using Org-mode
git-link - Emacs package to get the GitHub/Bitbucket/GitLab/... URL for a buffer location