See your GitHub Actions success/failure notifications in Slack without using additional actions in your workflow.

Trigger workflow runs once a team member has reviewed the PR manually.

Dynamically set values in your blog frontmatter when publishing using GitHub Actions

Prioritise PR reviews by receiving reminders via Slack on a fixed schedule.

Need to know what permission someone has on a repo before running a workflow? You can use either author_association or the /permission endpoint.

Backup your git repositories on a schedule using gickup. Do it to your NAS, and make it a "set and forget" backup process.

Allow the user to specify a Personal Access Token (PAT) in your GitHub Action whilst falling back to GITHUB_TOKEN by default

Using the wiki on GitHub makes life more difficult for your users, and you as a maintainer. Use the /docs folder and GitHub Pages instead and keep your docs in sync with code

Use a matrix to run your tests on new versions without failing the entire workflow run

Ensure that your workflows are always running with up to date data by fetching data dynamically at runtime

Learn how to build and use problem matchers with GitHub Actions + VSCode

A look at GITHUB_TOKEN, Personal Access Tokens and authenticating with GitHub Applications for GitHub Actions. Pros, cons and real world examples of when each option is the right choice.

Pin important issues to the top of your GitHub issues page. Useful for pending enhancements, common issues and items you're looking for help with

How to fix "Unable to push RubyGem to Package Registry (The expected resource was not found)"

Show all GitHub Actions being used by a user or organisation

Using arbitary branches for Actions is a risk, but as always it’s a compromise between security and making life easy for ourselves.



pin-github-action allows you to pin to a specific SHA whilst still pointing to a branch or tag