browser-hist.el VS gh-notify

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.

I highly recommend anticomputer/gh-notify for that.

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.

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