Started a discussion in open-sauced/open-sauced around every techies' favorite topic, naming things! A dire conquest to stay as neutral as possible, while still keeping a small semblance of relevance and utility in remembering, not what it's doing, but what you wanted to do over there!

The key takeaways or TL;DR:

1. Some repositories are in dire need of some more sensible naming, the more platforms a repo can be available on, the simpler the naming should be:
- @open-sauced/release <- @open-sauced/semantic-release-conventional-config
- @open-sauced/commit <- @open-sauced/conventional-commit
- @open-sauced/check-engines

2. Some of the very old and very new repositories could have their brand or code name repurposed as deployment environments while keeping a very small relevance suffix, descriptive of the application type, like:
- -action
- -integration
- -api
- -bot

What do you think they should be called? Join the @open-sauced discussions on GitHub and help decide (spoiler alert), what the hot sauce ingredients should really be called! 🍕🍕🍕

Matt and I continued to build out our GitHub action yesterday that Tweets to a first-time contributor once their pull request is merged into the main branch of a public repository.

• We got everything working except for sending out the actual Tweet, although we did output what would be Tweeted
• We learnt that some environment variables are not automatic.
• Tested the GitHub action some more with our test repository
• Here's our GitHub actions repository if you want to take a peek
  
  

Resources 

• Creating a composite action
• Creating a composite action
• Workflow syntax for GitHub Actions
• snow-actions/tweet repository
• The GITHUB_TOKEN in GitHub Actions: How it Works, Change Permissions, Customizations
• Output Multiline Strings in GitHub Actions

Thanks as always for hanging out with me on the stream Matt!

Sometimes when you start coding at 00:00 you want to stop at 00:00 and that's almost always going to be a bad idea. Guess what, 23 hours in, not even GitHub wanted us running any more workflows so they threw us a Thanksgiving surprise outage.

Closing in hot at 151 commits across 3 testing repositories, it's not about quantity but quality and this personal coding marathon milestone helped us progress preparations for the upcoming version 3 release of @open-sauced/semantic-release-conventional-config, a release so packed it's dropping version 4 on top of 3!

Meant to be a zero-config release companion to mtfoley/pr-compliance-action and a bold contender to the 2021 GitHub Actions Hackathon on DEV, it stays true to the @open-sauced pizza party, because what's better than releasing 🍕🍕🍕🍕🍕 with containerized GitHub actions?

Guess we'll just have to see!

Shoutouts @bdougie and @mtfoley!

Contributed to remirror/remirror

Had another fun stream with Matt Foley today. We continued work on the Github action to Tweet to a first-time contributor whose PR gets merged.

The GitHub action isn't finished yet, but we made some great progress. We were able to have the action return the Twitter handle from the user profile of the user that created the pull request.