Stop a running GitHub workflow when a release is on hold
A release hold should reach the active workflow quickly. Send the signal to Notis and cancel the matching run when it is 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
A workflow can keep running after a Backendless record signals that a release is on hold.
- Respond to release holds sooner.
- Avoid spending time on cancellable runs tied to a held release.
- Keep the cancellation decision connected to its source signal.
Setup
Build it in a few focused steps.
- 1Connect Backendless and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3In one instruction, tell Notis how to identify a release hold, find the related GitHub workflow run, and cancel it only if it is cancellable.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with one real hold signal and a cancellable run.
Questions about this workflow
Can the action cancel any workflow run?
It cancels a run only when GitHub reports it is in a cancellable state, such as queued or in progress.
What identifies the related run?
Specify the repository and any run identifying details in the instruction or make sure they are available from Backendless.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Backendless to GitHub. A trigger fires from one place; an action lands in another.
Backendless 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.
Backendless 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.