30 Minutes to Merge: GitHub Automation (11 AM PST)

What: In May’s edition of “30 Minutes to Merge”, we’ll be joined by special guest Gregor Martynus @gr2m.

Hi there :wave:

I’m the maintainer of the JavaScript Octokit – GitHub’s official JavaScript SDK.

If you have any questions about GitHub’s APIs or automation, and you think it would be interesting for others, too, please create an issue in my helpdesk repository. Questions by people new to coding are strongly encouraged! I do semi-regular live shows about exploring and hopefully answering your questions on my twitch channel: twitch.tv/gregorcodes

You can also ask and follow me on Twitter: twitter.com/gr2m

Past shows

Where: Live via GitHub Twitch, Q&A to follow the presentation in this event topic.

Prizes: There will be a swag giveaway for participants.


Event time is 11am PST | 2pm EST

Apologies for the multiple notifications!


💁🏻 30 Minutes to Merge: Automating nose booping using Actions
:date: Tuesday, May 25, 2021
:clock1: 11am Pacific Time (in your timezone)
:studio_microphone: hosted by @github(github.community event)
:label: Automation, Actions

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

This will be a a follow to the show on learnwithjason.dev: GitHub Automation with Octokit · Learn With Jason.

Together with @jlengstorf, we created a CLI to bump a nose-boop counter on Jason’s GitHub profile page at jlengstorf (Jason Lengstorf) · GitHub. We created a CLI and published it to npm. You can run it with npx boop-jasons-nose . It will create an issue in GitHub - jlengstorf/jlengstorf.

We then created a GitHub App and deployed it to Netlify functions. The app receives webhook requests for new issues, and then is using its own credentials to bump the nose-boop counter (function source code).

We planned to use GitHub Actions, but Actions experienced problems at the time of the show, so we skipped that part and used a GitHub App instead.



Starting in five minutes!
GitHub - Twitch

1 Like

Welcome to the GitHub community post event AMA, we are excited to be joined by @gr2m and @beardofedu.

We are standing by live to answer your questions. To submit a question, click “Reply”.

I’m happy to answer any question you got about today’s show :grin:


What’s your favorite GitHub action that you’d recommend to OSS maintainers, I have to ask!

1 Like

I know which one I’d love to have @gr2m suggest :wink:

1 Like

My favorite action is github.com/gr2m/twitter-together/. I built it myself, sorry for the plug, but I like it because it shows that GitHub Actions can be used so many interesting ways. I feel we didn’t scratch the surface yet.

I also really like the new “flat github” action, it’s a great way to pull data from other sources into your repository and publish it as open data: Flat Data · Actions · GitHub Marketplace · GitHub


ha! Definitely, yes, check out GitHub - check-spelling/check-spelling: Spelling checker action!



1 Like

@jsoref Hi ESL here, I need that in my life. Now. Also, for the dreaded “Github”


@gr2m got any open source projects that could use some love from the community? Especially those with lower barriers of entry?

1 Like

what is a github action you think someone should have on every repository?

1 Like

I’m constantly sending PRs and issues about Github. Sadly that’s a bit harder since by default I tolerate Foo if foo is in the dictionary. But I will probably make a rule to allow rejecting it, since Javascript is also on my naughty list. (Maybe in .20, I’m already close to shipping .19.)

But w/ the current release, it’s pretty easy to set up. And I can be found on Probot :robot: Slack.

1 Like

I could not live without automating my releases using semantic-release. We don’t have an official action, but it’s easy enough to use directly using npx semantic-release.

The amount of time release automation saves me across my hundreds of repository, and the amount of errors I’d do if it wasn’t automated, cannot be underestimated.

For example, here is the release setup for the octokit package:


What would be helpful is if the Marketplace were to reject things like Github and Javascript listings :wink:



I’d argue that any repository that has English text (which is roughly everything) should have a spell-checker. Obviously it needs to be able to understand how programmers write text.

I’m biased, since I maintain one.

For sufficiently large repositories, a good spell checker will find bugs that mean code is being tested incorrectly. They can also protect against embarrassing content.

1 Like

super cool, thank you for sharing! and thanks to you all for the stream + post