Stop duplicate GitHub work when Buildkite fails
A failed Buildkite build can leave related GitHub runs consuming time. Let Notis check the run state and cancel it when it is still cancellable.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Cancel a workflow run
Cancels a workflow run in a github repository if it is in a cancellable state (e.g., 'in progress' or 'queued').
Why this helps
You have to switch between Buildkite and GitHub to stop work that is already known to be failing.
- Stops related queued or active GitHub runs after a failure is reported.
- Reduces manual checks across build tools.
- Avoids cancelling runs that are no longer cancellable.
Setup
Build it in a few focused steps.
- 1Connect Buildkite and GitHub to Notis once in the portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3In one instruction, tell Notis to use the Buildkite failure details to find and cancel the related cancellable GitHub workflow run.
- 4Choose the Notis webhook trigger and select where run reports should go.
- 5Send one real Buildkite failure event to test the automation.
Questions about this workflow
Does Buildkite provide a Notis trigger event for this workflow?
No. Start it with a Notis webhook that receives a Buildkite event request.
Will it cancel every GitHub run?
No. Tell Notis how to identify the related run from the event details, and have it cancel only a run that is cancellable.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Buildkite to GitHub. A trigger fires from one place; an action lands in another.
Buildkite triggers
GitHub actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List repositories starred by the authenticated user
Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.
Add app access restrictions
Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.
Add a repository collaborator
Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.
Add a repository to an app installation
Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Connect any two apps with Notis in the middle.
Buildkite and GitHub, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business GitHub.