Cancel outdated Pages deployments automatically
Keep a stale deployment from becoming tomorrow's problem.
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 deployment started under old market assumptions may finish long after the underlying decision has changed.
- Limits outdated releases
- Cuts down on deployment babysitting
- Adds a clear market-aware guardrail
Setup
Build it in a few focused steps.
- 1Connect Finage and GitHub to Notis once via the portal.
- 2Create the automation in the portal or ask Notis to cancel the specified ongoing GitHub Pages deployment when Finage meets the stated condition.
- 3Select a recurring trigger and the channel for run reports.
- 4Test with one active or queued Pages deployment.
Questions about this workflow
What kind of condition can I describe?
Describe the market threshold or change that makes the deployment no longer appropriate.
Does this publish a replacement?
No. This workflow only cancels the specified GitHub Pages deployment.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Finage to GitHub. A trigger fires from one place; an action lands in another.
Finage triggers
GitHub actions
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
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.
Not just Finage and GitHub. Any 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.