Published a new article, Semantic release to npm and/or ghcr without any tooling, as a new submission to the 2021 GitHub Actions Hackathon on DEV, showcasing how we made our semantic-release shareable configuration available to the world without installing any local dependencies, using GitHub marketplace actions or container based actions.

The post is deeply technical, covering our motivations for some architectural decisions, how we simplified our configuration, preset defaults and how to manipulate them without forking;

The covered use cases for this action:
- any kind of public npm package
- containerized NodeJS application
- containerized NodeJS GitHub action

And the different ways we can run this action from:
- npm devDependencies (not advised)
- GitHub container registry package
- GitHub marketplace action

Here are all the open source actions we used throughout the post to demo different use cases:
- actions/checkout@v2 - most performant git checkout
- actions/setup-node@v2.1.5 - we use it to set the node version to 16
- actions/upload-artifact@v2 - we use it to transport our artifacts in between jobs
- actions/download-artifact@v2 - we use it to download our artifacts in between jobs
- docker/setup-buildx-action@v1 - we use it to setup the docker builder
- actions/cache@v2 - we use it to cache docker layers
- docker/metadata-action@v3 - we use it to normalise most of our docker container values
- docker/build-push-action@v2 - we use this to build the container
- bahmutov/npm-install@v1 - lightning fast npm ci with built-in cache
- open-sauced/semantic-release-conventional-config@v3 - semantic-release configuration, docker container and GitHub action
- geekyeggo/delete-artifact@v1 - deletes produced artifacts

Published a new article, How to lint PRs and welcome contributors using GitHub Actions, as a new submission to the 2021 GitHub Actions Hackathon on DEV, showcasing how we are using GitHub Actions reusable workflows across the @open-sauced GitHub organization.

The post succinctly details the issues we faced having to update compliance workflows across different repositories while encouraging other open source maintainers to apply a similar practice, centralizing high impact workflows and re-using them from GitHub tags or long SHA commits.

Here are all the open source actions we are using to power this compliance workflow:
- actions/first-interaction@v1 - welcomes first-time contributors with a custom message
- amannn/action-semantic-pull-request@v3.4.0 - ensures pull request title matches conventional commits specification
- mtfoley/pr-compliance-action@v0.2.1 - check pull request for compliance on title, linked issues, and files changed

Published a new article, Automatically update git major tags on GitHub marketplace release, as a new submission to the 2021 GitHub Actions Hackathon on DEV, showcasing a 99% automated way of releasing and maintaining GitHub actions.

From a non-technical perspective, the post details the poorly documented steps needed to enable acceptance testing to marketplace actions, something possible with our release configuration and the described tag action.

This is all possible by leveraging all these GitHub marketplace actions:
- Actions-R-Us/actions-tagger@v2 - updates major tag on release
- @open-sauced/semantic-release-conventional-config@v3 - takes care of releasing everything up to the marketplace release

Published a new article, Generate PDF handbook with Docusaurus using GitHub Actions, as a new submission to the 2021 GitHub Actions Hackathon on DEV, showcasing our experience in generating a downloadable handbook from our @open-sauced documentation endpoint.

From a more technical perspective, the post details the additional workflow steps we had to add to make this possible:
- build, cache, and store a docker container as a build artifact
- mount the docs as a docker container service
- install Prince 14 binary
- make the generated pdf asset available

This is all possible by leveraging all these GitHub marketplace actions:
- actions/checkout@v2 - most performant git checkout
- actions/setup-node@v2.1.5 - we use it to set the node version to 16
- actions/upload-artifact@v2 - we use it to transport our artifacts in between jobs
- actions/download-artifact@v2 - we use it to download our artifacts in between jobs
- docker/setup-buildx-action@v1 - we use it to set up the docker builder
- actions/cache@v2 - we use it to cache docker layers
- docker/metadata-action@v3 - we use it to normalize most of our docker container values
- docker/build-push-action@v2 - we use this to build the container
- bahmutov/npm-install@v1 - lightning-fast npm ci with built-in cache
- open-sauced/semantic-release-conventional-config@v3 - semantic-release configuration, docker container and GitHub action
- peaceiris/actions-gh-pages@v3 - deploys any folder(s) to gh-pages, can use it for multiple static endpoints
- geekyeggo/delete-artifact@v1 - deletes produced artifacts

Made a valuable contribution to open-sauced/semantic-release-conventional-config, releasing a new version with added features and bug requests:
- ability to run the semantic configuration as a Dockerfile container or a GitHub marketplace action removing npm install necessity  - simplifies the release workflow by defaulting all environgent variables except GITHUB_TOKEN and NPM_TOKEN - configuration detects Dockerfile and action.yml configuration
- fixes a [skip ci] bug in alpha and beta pre-release branches
- adds better usage documentation and examples to the README
- adds license update plugin and git asset configuration
- adds emojis to changelog generation 

Made a valuable contribution to open-sauced/docs.opensauced.pizza, releasing a new version with added documentation for @open-sauced/conventional-commit, updated documentation for @open-sauced/semantic-release-conventional-config and improved release workflow.

It's still missing some emojis but contributions are always welcome! 🍕