Cancel stale workflows in member demo repositories
On a schedule, Notis can cancel specified queued or in-progress GitHub workflow runs for temporary repositories used in Membervault demos.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
Old demo runs create noise and make it harder to see the work that still needs attention.
- Reduces distracting build noise
- Keeps temporary demo environments easier to read
Setup
Build it in a few focused steps.
- 1Connect Membervault and GitHub to Notis once.
- 2Create an automation and select a recurring schedule.
- 3Prompt Notis to cancel stale specified workflow runs in member demo repositories, choose reports, and test with a cancellable run.
Questions about this workflow
Will it cancel completed runs?
No. GitHub only cancels workflow runs that are in a cancellable state.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Membervault to GitHub. A trigger fires from one place; an action lands in another.
Membervault 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.
Membervault 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.