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

Content is a mainstay of many Developer Relations teams, but it can sometimes be tough to show the impact that you’re having. The best way I’ve found to justify your existence (and yes, unfortunately this is a thing in every business) is to attach yourself to the revenue generating teams. Read more to find out how

Learn how I use Pocket to keep track of things I want to read, and then actually read them!

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.

Automatically ignore any automated changes in git blame by ignoring specific commits

Use Netlify Functions and their on-demand build functionality to generate OpenGraph images just in time and persist them on a CDN to reduce your serverless costs

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