Go-github: Automating the sync between GitHub API Blog and our library

[kshitij10496]

I noticed that we currently have to manually create a New Issue every time there is an announcement from GitHub API Blog (usually on a weekly basis). How about we automate this bookkeeping process so as to save some effort?

I would like to share a way we can implement this:
Step 1: Using an RSS feed parser (such as gofeed) to notify about updates
Step 2: Using go-github itself to create new issues every time there is an update.

Currently, I intend to implement this a simple program or script which one can run as an hourly cronjob. We can create a bot account similar to googlebot which reports these updates on our Issues tracker.

This will ease the load of the project maintainers, especially @gmlewis from having to manually keep track of updates from GitHub. I might have overlooked some important details in the Proof-Of-Concept above but I would love to listen to what the developers think about this proposal and whether this would be a useful addition to the project.

Ping @willnorris @gmlewis @shurcooL @sahildua2305 @anubhakushwaha

[willnorris]

Not ever post on the GitHub API blog requires action. It always requires a human to read the post and determine if we need to do something with the information. I don't see how you can automate that.

[gmlewis]

I think that's a fantastic idea, @kshitij10496!

The only downside I could think of is that some of their announcements don't affect this project, but that is extremely rare... I think I've only seen one or two in the past year that were a no-op for this repo... and if we decide to go forward with this, then those issues could simply be closed as "Not an issue for this repo."

[kshitij10496]

Not ever post on the GitHub API blog requires action. It always requires a human to read the post and determine if we need to do something with the information.

Absolutely.
We should intend to use this as a notification service which notifies us about recent development from GitHub's end. After reading the changes mentioned in the update, we can discuss on how to proceed with the implementation same as the current process.

Moreover, even if an update requires no changes from our side, we will have an organized and transparent way to consciously take this decision. As @gmlewis mentioned above, we can simply close the irrelevant issues.

[sahildua2305]

Great idea, @kshitij10496

[elliott-beach]

@kshitij10496 Are you planning on working on this? If otherwise, I would be interested in doing this.

[kshitij10496]

@elliott-beach I have created a script for this but I am having some issues with synchronizing the items in the feed. So, I would like to take some time to figure them out.
In case I don't make any progress, feel free to take this up by the next weekend. 😄

[kshitij10496]

@gmlewis There seems to be some confusion with regards to the issue number in my commit message. I distinctly remember making a mistake in referencing the correct issue in b165831.
Since you have merged this PR into the master, GitHub is closing this issue due to the commit message. I believe we need to amend the commit message so that it refers the correct issue (#835) in this case.

[gmlewis]

Ah, yes... you are right, @kshitij10496.
I'm sorry about that.

@shurcooL - to amend the commit message, do I need to revert that commit (#844) and then issue a new commit with the fixed message?

[dmitshur]

@gmlewis Sorry about the response delay, my notifications overflowed.

It's not possible amend the commit message after it's been pushed to master, not without force pushing. I don't think it's worth it to revert the commit—it's just a commit message. It's unfortunate that it has the wrong issue number, but not critical. People can follow the links and figure out what happened. We can just reopen/close issues as needed and move on.

[gmlewis]

OK, sounds good. Thank you, @shurcooL!

[kshitij10496]

Hello everybody!

It feels good to be back here. 😄
Just a catch up, I did an internship at BubbleStudent this Summer developing microservices using Go.
I'm grateful to all of you, the community for helping me get started with Go and evolve as a developer over the past year. 🙏