browser-hist.el
code-review
Our great sponsors
browser-hist.el | code-review | |
---|---|---|
3 | 15 | |
28 | 448 | |
- | - | |
10.0 | 0.0 | |
over 1 year ago | 6 months ago | |
Emacs Lisp | Emacs Lisp | |
GNU General Public License v3.0 only | GNU General Public License v3.0 only |
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.
browser-hist.el
-
Is orgmode really that much better than an equivalent workflow using vim + other tools?
Next, I needed to open a related project, which I didn't have locally. So, finally, I had actually to open my browser. Note that everything I described to this point, all, was done solely in Emacs. But wait, we're not ready to switch just yet. Now, I remembered that I already had to open that repo last week, so I searched through my browser history and found the link to it. , and now I'm in the browser. I searched, and I found the document I needed, and I decided - that still didn't warrant cloning the entire project. "I'm just gonna copy the link and put it in my note...". The inserted link would've been something like https://github.com/booga/wooga/pulls/4110. But not in Emacs, no. Since I'm using Org-mode, I customized org-link-make-description-function. What it lets you do, is to write your custom function, and that's what I did. My function goes to GitHub and pulls the description of the PR #4110. And now my link looks like this: Fixes migration in the Orchestration Module booga/wooga#4110.
- browser-hist.el: Search through browser history, in Emacs
- New package. Status: experimental. Early feedback is appreciated.
code-review
-
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.
What are some alternatives?
evil - The extensible vi layer for Emacs.
magit - It's Magit! A Git Porcelain inside Emacs.
org-noter - Emacs document annotator, using Org-mode
gist.el - Yet another Emacs paste mode, this one for Gist.
spacehammer - Hammerspoon config inspired by Spacemacs
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)
neorg - Modernity meets insane extensibility. The future of organizing your life in Neovim.
github-review - Github code reviews with Emacs.
neogit - An interactive and powerful Git interface for Neovim, inspired by Magit
org-roam - Rudimentary Roam replica with Org-mode
git-link - Emacs package to get the GitHub/Bitbucket/GitLab/... URL for a buffer location