GitHub provides an RSS feed for all user-facing changes made on the platform
1–10 of 21 posts
Re: GitHub provides an RSS feed for all user-facing changes made on the platform
#2Re: GitHub provides an RSS feed for all user-facing changes made on the platform
#3Re: GitHub provides an RSS feed for all user-facing changes made on the platform
#4I wish more companies were doing this. What could be the factor that would prevent all companies to do the same, apart from laziness? Am I the only one interested by the changes that are made on the tools that I like? I'm the kind of guy who reads all release notes.
Re: GitHub provides an RSS feed for all user-facing changes made on the platform
#5They also provide a Twitter account by the way: https://twitter.com/GHChangelog
Re: GitHub provides an RSS feed for all user-facing changes made on the platform
#6I wish more companies were doing this. What could be the factor that would prevent all companies to do the same, apart from laziness? Am I the only one interested by the changes that are made on the tools that I like? I'm the kind of guy who reads all release notes.
1. Create a GitHub Repo dedicated to user-facing issues (https://github.com/scoutapp/roadmap)
2. Customers can subscribe to issues they are interested.
3. When resolving an issue, we reference it in the git commit, which closes the issue and notifies the issue subscribers.
We're a developer tool, so it's a familar flow for our customers.
Re: GitHub provides an RSS feed for all user-facing changes made on the platform
#7Re: GitHub provides an RSS feed for all user-facing changes made on the platform
#8https://blog.github.com/feed.xml" title="The GitHub Blog" />
To this:
https://blog.github.com/changelog/all.atom" title="The GitHub Blog" />
Right now there's 3 different RSS things on the page, and 2 of them go to the wrong place.
Re: GitHub provides an RSS feed for all user-facing changes made on the platform
#9I wish more companies were doing this. What could be the factor that would prevent all companies to do the same, apart from laziness? Am I the only one interested by the changes that are made on the tools that I like? I'm the kind of guy who reads all release notes.
A lightweight approach we've started at my company: 1. Create a GitHub Repo dedicated to user-facing issues ( https://github.com/scoutapp/roadmap ) 2. Customers can subscribe to issues they are interested. 3. When resolving an issue, we reference it in the git commit, which closes the issue and notifies the issue subscribers. We're a developer tool, so it's a familar flow for our customers.