Stop a linked GitHub run when a severe regression is reported
Use a clear severity rule and a run identifier from the report to stop a cancellable GitHub workflow run when a severe regression arrives.
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
A severe performance regression can leave a related GitHub run consuming time while the team is still investigating.
- Act on a severity rule you define in the prompt.
- Avoid continuing a cancellable run linked to a severe regression.
- Keep the repository and run target grounded in supplied data.
Setup
Build it in a few focused steps.
- 1Connect Blazemeter and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, with a name and prompt.
- 3In one instruction, tell Notis to cancel only a cancellable workflow run when the webhook meets your severe regression rule and supplies the repository and run identifier.
- 4Pick the Notis webhook trigger and choose where run reports go.
- 5Test with one real example and confirm the severity rule and run identifier before enabling routine use.
Questions about this workflow
Will it cancel every run after any regression?
No. Specify the severity condition in the prompt and have Notis act only when the report meets it.
What if the webhook does not include a GitHub run identifier?
The action requires a target run. Provide the repository and run identifier in the report or prompt; otherwise, the automation should not cancel a run.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Blazemeter to GitHub. A trigger fires from one place; an action lands in another.
Blazemeter 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.
Blazemeter 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.