💁🏻 Automating gr2m/helpdesk: issue forms
📅 Monday, June 28, 2021
🕐 12:05pm Pacific Time (in your timezone)
🎙️ no guests
🏷️ Automation

Subscribe to this issues to get a notification before the show begins and a summary after the show concludes.

Automating gr2m/helpdesk: issue forms

After focusing on automating README updates, issue comments and tweets in the previous automating helpdesk shows, I'll work this week on the newly announced issue forms.

Instead of creating new show issue by copying previous ones, it's about time to streamline the process. Maybe issue forms are not ideal for that purpose, but it's better than what I have right now and it will be fun to explore it.

Outline

1. Walk through the new markdown issue forms and how they work
2. Show the two templates created for this repository: one for show ideas suggest by y'all, and the other a show template that is for my own shows.

TODOs

Before the show

• Prepare two show templates: one for show ideas, one for actual shows.
• 30 minute announcement tweet
  (https://twitter.com/gr2m/status/1409584061673218052)
• 30 minute announcement comment
  (📅 6/28 @ noon PT - Automating gr2m/helpdesk: issue forms #34 (comment))

When show begins

• start of show tweet
  (https://twitter.com/gr2m/status/1409588976457969666)
• comment on issue
  (📅 6/28 @ noon PT - Automating gr2m/helpdesk: issue forms #34 (comment))
• Set twitter profile url to https://twitch.tv/gregorcodes
  (https://twitter.com/gr2m)

After the show

• Reset twitter profile after the show
  (https://twitter.com/gr2m)
  (https://twitter.com/gr2m)
• recording available tweet

Recording

will be added after the show

Shownotes

• documentation for issue forms: https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms
• Issue parser action: https://github.com/stefanbuck/github-issue-parser