A tried and tested workflow for designing OpenAPI schemas that inherit from each other using allOf.

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

Support both mylib() and mylib.myfunc() in the same package using Object.assign()

Ensure that all the HTTP calls you're expecting an SDK to make are being made. Test POST bodies, error handling and any other part of the request/response that you like

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.

Kong Gateway 3.0 brings with it Secrets Management to manage all of your sensitive information. Learn more!

Kong Gateway 3.0 delivers enhanced security and governance, greater flexibility and extensibility, and significant performance improvements.

Find out how to use StepZen and Kong Gateway plugins to build an API endpoint that shows the price of an item in a user’s local currency.

Want to manage multiple sets of configuration for Kong Gateway through a single interface? Now you can. Check out Runtime Groups for Kong Konnect.

Configure all traffic to flow through a VPN for a set of docker-compose services

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

If you’ve been online at all this week, chances are that you’ve heard about the Log4Shell zero-day (CVE-2021-44228) in Log4J, a popular Java logging library. The vulnerability enables Remote CodeContinue reading

...

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.

In this tutorial, we’ll create a new AWS security group and EC2 instance on Pulumi and then provision it as a Kong Konnect data plane.

Event hooks allow you to get notifications when certain events happen on your Kong Gateway deployment. Here's how they work...

One common comparison I see is ServiceHub vs. Dev Portal. Do you need both? If so, how do they complement each other?

Netlify on-demand builders are great, but how do you test Puppeteer + functions locally?

In this tutorial, I’ll go through the process of moving from Kong Gateway OSS to Konnect. It’ll take about 20 minutes if you want to work through it too.

In this tutorial, you'll learn how to build a Kong Gateway plugin with JavaScript. We’re going to implement a plugin that adds X-Clacks-Overhead.

See all the information available to your workflows in the logs by including a single composite action

Automatically approve workflow execution from new contributors if they're safe to approve

Read the frontmatter from your markdown files and use the values in your workflows

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

Process a YAML document and make all the elements available as GitHub Workflow output variables

Access url friendly versions of GITHUB_* environment variables in your workflows

Commit and push local changes then raise a pull request automatically in a GitHub Actions workflow

Use a circuit breaker to stop Laravel job queue execution when you hit your GitHub rate limit

Push any committed changes back to your repo automatically using the provided GITHUB_TOKEN

Push changes made to a repo during a GitHub Actions workflow run. Supports adding and removing files + pulling changes if needed

Automatically commit files that change during a workflow run and push them back to GitHub

Fail the build unless a certain combination of labels are applied to a pull request

Merge pull requests automatically on a scheduled day

Create additional records whenever a new team is created using the TeamCreated event

Run your tests in separate database with Laravel Sail

Convert Docker based Actions to use the Node runtime automatically for lightning fast GitHub Actions!

Use this GitHub Action as a continuous integration check to ensure that all the actions you depend on are pinned to a SHA

Show all GitHub Actions being used by a user or organisation

Automatically add a reviewed-by trailer using GitHub code reviews and a GitHub Action

Fetch all pages of results from the GitHub API by following the Link header using Bash

Handle multiple event types in a single GitHub Action by routing using GITHUB_EVENT_NAME and the payload action

Make your v1 tag point at the latest commit automatically as you tag v1.2.0, then v1.2.1, v1.3.0 and so on

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

A step-by-step guide to building a GitHub Action using Javascript and actions-toolkit

Learn how to test your GitHub Actions and Workflows on your local machine with nektos/act; which uses Docker and Go to emulate the Actions runner

Define and run JavaScript based GitHub Actions with Docker