{"id":11837,"date":"2019-01-30T03:25:54","date_gmt":"2019-01-30T08:25:54","guid":{"rendered":"https:\/\/rud.is\/b\/?p=11837"},"modified":"2019-01-30T03:25:54","modified_gmt":"2019-01-30T08:25:54","slug":"quick-hit-using-seymour-to-subscribe-to-your-gitlahub-repo-issues-in-feedly","status":"publish","type":"post","link":"https:\/\/rud.is\/b\/2019\/01\/30\/quick-hit-using-seymour-to-subscribe-to-your-gitlahub-repo-issues-in-feedly\/","title":{"rendered":"Quick Hit: Using seymour to Subscribe to your Git[la|hu]b Repo Issues in Feedly"},"content":{"rendered":"

The seymour<\/code>?<\/a> Feedly API package has been updated to support subscribing to RSS\/Atom feeds. Previously<\/a> the package was intended to just treat your Feedly as a data source, but there was a compelling use case for enabling subscription support: subscribing to code repository issues. Sure, there’s already email notice integration for repository issues on most social coding platforms but if you always have Feedly up (like I usually do) having issues aggregated into a Feedly category may be a better way to keep tabs on what’s going on.<\/p>\n

If you use GitLab, that platform already has RSS feeds for public repositories. GitHub users have to use either RSSHub<\/a> or gh-feed<\/a> to do the same (note that you can host your own instance of either of those tools).<\/p>\n

If you have more than a few repos and want to have their issues shunted to Feedly you could<\/em> go manually enter them into the Feedly UI but that could be a pain, especially if “more than a few” is in the dozens or hundreds. But, we have R and can automate this. I’m providing an example for GitHub (since most readers art still stuck on that legacy platform) via the gh<\/code> package but the same methods can be done for GitLab using the gitlabr<\/code>?<\/a> package.<\/p>\n

First, we need to get the list of public GitHub issues you own:<\/p>\n

library(gh)\nlibrary(purrr)\nlibrary(seymour) # git.sr.ht\/~hrbrmstr\/seymour, git[la|hu]b\/hrbrmstr\/seymour\n\ngh::gh(\n  \"\/user\/repos\", \n  visibility = \"public\",\n  affiliation = \"owner\",\n  sort = \"created\", direction = \"desc\", \n  .token = Sys.getenv(\"GITHUB_PAT\") # see ?devtools::github_pat\n) -> gh_repos\n<\/code><\/pre>\n
If you have more than 30 the gh<\/code> package has a gh_next()<\/code> function which will enable you to paginate through all your repos.<\/p>\n
Now you need to choose between gh-feed or RSSHub and prepend a special URL prefix to a user\/repo<\/code> string to create a usable RSS URL. These are the prefixes:<\/p>\n