Cancel stale Pages deployments
Prevent paused launches from continuing to publish by accident.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Cancel a GitHub Pages deployment
Cancels an existing, ongoing or queued github pages deployment for a repository using its `pages deployment id`.
Why this helps
A paused customer launch can still have a deployment waiting in GitHub.
- Fewer accidental publishes
- Cleaner launch control
- Reduced deployment noise
Setup
Build it in a few focused steps.
- 1Connect Close and GitHub in Notis once.
- 2Create a new automation in Automations.
- 3Tell Notis to cancel the GitHub Pages deployment identified for each paused Close launch.
- 4Choose a recurring schedule and a report channel.
- 5Test with one paused launch.
Questions about this workflow
Can completed deployments be canceled?
No, the action handles ongoing or queued deployments.
What identifier is needed?
Provide the repository and Pages deployment id in the automation context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Close to GitHub. A trigger fires from one place; an action lands in another.
Close 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.
Close 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.