Malleable Computing, Emacs, and You
A developer shares their process for automating the synchronization of GitHub issues with Emacs Org Agenda. The article details the use of the GitHub CLI and various Elisp packages to create a seamless workflow for managing public projects.
Why it matters
It demonstrates the power of 'malleable computing' and how developers can customize their environments to bridge the gap between disparate productivity tools.
It all started with a routine task. I use GitHub issues for all of my public-facing projects but my preference is keeping track of things in Org Agenda. To reconcile the two, I would manually copy over the GitHub issue to an Org file, typically the title and description, like an animal .
Despite this separation, the duplicated issue allowed me to treat it as a scratchpad for anything I could express in Org. In this way, I used the duplicated issue in Org as both a dedicated area to take notes and a “staging” area to compose follow-up comments that I’d want to share in the public facing issue.
I manually copied for far longer than I care to admit. Repeat a task enough times in Emacs and the inevitable thought arises: “I should automate this.”
Get smarter about the news
Sign up free for a feed built around what you actually care about, Dive Deeper research on any story, and the full text of every article.
Create free accountAlready have an account? Sign in