browser-hist.el VS code-review

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.

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.

If I want to review a PR, there's code-review.

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)

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

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.

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.

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.