Give Buildkite failure follow-up an owner
When the event points to both an issue and an assignee, Notis can update the GitHub issue so the next action is clear.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add assignees to an issue
Adds or removes assignees for a github issue; changes are silently ignored if the authenticated user lacks push access to the repository.
Why this helps
A failure may be understood, but nobody is clearly responsible for the issue it affects.
- Makes ownership visible in the issue tracker.
- Cuts the manual step between build monitoring and issue follow-up.
- Can add or remove assignees based on the event and instruction.
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 issue ownership.
- 3In one instruction, tell Notis to assign the matching GitHub issue only when the Buildkite details identify a valid issue and assignee.
- 4Choose the Notis webhook trigger and select where run reports should go.
- 5Test with one real event that includes a known issue and assignable GitHub user.
Questions about this workflow
Will it guess who owns the issue?
Tell Notis to assign only when the event or your instruction provides a clear assignee.
What if the user cannot be assigned?
The automation should report the result so you can resolve the assignment 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.