Stop obsolete GitHub runs after media publishing fails
Keep a failed Cincopa publish from leaving a related queued or in-progress GitHub run consuming attention.
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
An obsolete build or deployment run can keep going after the media it depends on failed to publish.
- Avoid watching obsolete runs
- Reduce confusion around failed media releases
- Keep run status aligned with the publishing outcome
Setup
Build it in a few focused steps.
- 1Connect Cincopa and GitHub once in Notis.
- 2Create an automation in the portal or tell Notis to create one in plain language.
- 3Ask Notis to match a Cincopa publish failure to its related GitHub run and cancel it only when it is queued or in progress and no longer needed.
- 4Choose the Notis webhook trigger and configure the sender to make an HTTP request to it.
- 5Choose a report channel and test with one real failure and a cancellable run.
Questions about this workflow
Can this cancel every GitHub run?
The instruction should identify only the run made obsolete by the reported publishing failure. GitHub cancellation works only for runs in a cancellable state.
What if the report does not identify a run?
Include enough repository and workflow context in the report for Notis to identify the correct run, or have Notis report that it could not match one.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Cincopa to GitHub. A trigger fires from one place; an action lands in another.
Cincopa 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.
Cincopa 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.