Keep recurring build problems visible in GitHub
A recurring review can turn Buildkite failure patterns into labeled GitHub issues, helping repeated problems stay on the team's radar.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Add labels to an issue
Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
Why this helps
A recurring failure can blend into a busy build history and never become visible issue follow-up.
- Surfaces matching issues with a useful triage label.
- Connects periodic build review to issue follow-up.
- Avoids relying on memory to notice repeat failures.
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 name it for recurring failure triage.
- 3In one instruction, tell Notis what Buildkite failures to review, how to find a related GitHub issue, and which label to add.
- 4Choose a recurring Notis schedule and select where run reports should go.
- 5Test with one real failure and a matching GitHub issue.
Questions about this workflow
Will this detect a trend automatically?
Describe the failure pattern to review and make sure the relevant Buildkite history is available to Notis.
What if the matching issue is unclear?
Instruct Notis to report uncertainty instead of labeling an unrelated issue.
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.