Stop the GitHub run tied to a halted CircleCI deployment
When a deployment halt identifies the corresponding GitHub workflow run, let Notis stop that queued or in-progress run and report what happened.
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 deployment may be halted in CircleCI while a related GitHub workflow continues running and needs a separate manual stop.
- Reduce duplicate or obsolete workflow work
- Use the run identifier supplied by the deployment notice
- Get a report if the GitHub run cannot be cancelled
Setup
Build it in a few focused steps.
- 1Connect CircleCI and GitHub once in Notis.
- 2Create an automation and describe the deployment stop outcome.
- 3In one instruction, tell Notis to cancel only the GitHub workflow run explicitly identified by a CircleCI deployment halt, and only when the run is queued or in progress.
- 4Pick a webhook trigger and choose where run reports should go.
- 5Test with one real halt notification that identifies a GitHub workflow run.
Questions about this workflow
Will this cancel a run based only on a failed CircleCI build?
No. Instruct Notis to require an explicit deployment halt and the corresponding GitHub workflow run identifier.
Can every GitHub run be cancelled?
The listed action cancels runs only when they are in a cancellable state, such as queued or in progress.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Circleci to GitHub. A trigger fires from one place; an action lands in another.
Circleci 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.
Circleci 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.