Give recurring build follow-up a clear owner
When a scheduled Buildkite review finds a failure with a known issue and owner, Notis can assign the GitHub issue and make follow-up visible.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
Recurring build problems may be known by the team but still lack an assigned next step.
- Makes issue ownership explicit when context supports it.
- Links recurring build review to an actionable GitHub update.
- Reduces the chance that follow-up stays unassigned.
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 build follow-up ownership.
- 3In one instruction, tell Notis which Buildkite failures to review and to assign only a matching GitHub issue with a clearly identified assignee.
- 4Choose a recurring Notis schedule and select where run reports should go.
- 5Test with a real failure, matching issue, and assignable user.
Questions about this workflow
Will it assign a user based on guesswork?
No. Instruct it to make an assignment only when a valid assignee is clear from the available context.
What if GitHub ignores the assignment?
The action can silently ignore changes when the authenticated user lacks push access, so check run reports and permissions.
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.