Answering all your (and some of my own) GitHub API/automation questions live at twitch.tv/gregorcodes
Got any questions or ideas? You can
- Ping me on twitter: @gr2m
- Create an issue in this repository
- Refactoring a 10+ years old code base: nock (Part VII)
- Refactoring a 10+ years old code base: nock (Part VI)
- Refactoring a 10+ years old code base: nock (Part V)
- Refactoring a 10+ years old code base: nock (Part IV)
- Refactoring a 10+ years old code base: nock (Part III)
- Refactoring a 10+ years old code base:
nock(Part II) - Refactoring a 10+ years old code base:
nock - Automating gr2m/helpdesk: Twitch Events
- Creating tests for actions for faster iteration Part III
- Creating tests for actions for faster iteration Part II
- Creating tests for actions for faster iteration
- Automating gr2m/helpdesk: Issue Forms part III
- Automating gr2m/helpdesk: issue forms part II
- Running scheduled GitHub App tasks using Actions
- Automating gr2m/helpdesk: issue forms
- How to update lock files silently (Part III)
- Automating gr2m/helpdesk: comment on issue when show begins
- Advanced TypeScript for the future Octokit SDK with @orta
- Automating gr2m/helpdesk, Episode VI
- Automating gr2m/helpdesk, Episode V
- How to update lock files silently (Part II)
- How to update lock files silently
- Automating gr2m/helpdesk, Episode IV
- transfer issues + comments between repositories while retaining authorship, labels, and milestones
- 30 Minutes to Merge: Automating nose booping using Actions with @github
- Automating gr2m/helpdesk, Episode III
- copy GitHub repositories with issues, labels, milestones, and assignees
- Automating gr2m/helpdesk, Episode II
- Slash commands & rebasing pull requests with @davidguttman
- Learn with Jason: GitHub Automation with Octokit with @jlengstorf
- Automating gr2m/helpdesk, Episode I
- Script Kit meets Octokit with @johnlindquist
- GitHub Action Artifacts with @reconbot
- Octokit automation: OpenAPI
- Create a
cowsayGitHub Action with JavaScript - GitHub Enterprise repository auditing with @jeffwilcox
I keep track of how I use this repository over time as I hope to automate most of it eventually 😂
A show usually starts out with an idea on twitter, such as the idea to audit repository access using GitHub Actions. If we agree to make a show about it, I turn it into an issue with a 🏷 show label such as 📅 4/29 @ 1pm PT - GitHub Enterprise repository auditing with @jeffwilcox. If the idea needs some more research, I turn it into an an issue with an 🏷 idea label such as 💡 How to use Environments + Secrets.
I add all 🏷 show issues to this README as well as on https://github.com/gr2m/gr2m.
I use the issue for preparation, to make sure the guests (if any) and I are on the same page, and to have a rough outline of steps I want to go through during the show. I try to keep the shows to 30 minutes and getting stuck in an unforeseen problem could blow that time limit very quickly, so I like to be prepared. I invite everyone interested in the show to subscribe to the issue.
When the show goes live, I add a comment with a link to twitch.tv/gregorcodes, and also send a tweet that the show is going live shortly.
After the show I add a comment to the Twitch recording for people who missed the live show. I also add notes from the show.
Then I upload the recording to YouTube and add another comment with a link to the video on YouTube, as this one won't be removed after 14 days.
After that, I close the issue, and move the show to the "Past" section in this README as well as on https://github.com/gr2m/gr2m
My goal is to automate everything about my helpdesk show that can be automated. You can find a list of past and upcoming shows about automating helpdesk at https://github.com/gr2m/helpdesk/issues?q=label%3A%22automating+helpdesk%22
- automate "Upcoming shows" / "Past shows" sections in the repository README — #10
- automate "Upcoming shows" / "Past shows" sections on my profile page — #10
- add a comment to the issue when I go live on twitch
- Schedule tweet 30 minutes before the show goes live
- Schedule tweet when the show goes live
- add comment with a link to the twitch recording once it's available
- Send out tweet when the video is available on YouTube
- add a comment with a link to the video on YouTube once it's available in maximal resolution
- figure out a way to populate show notes from twitch comments