Keep stale GitHub Actions runs from lingering
Give Notis your rule for a run that has lingered too long. It can review available run details and cancel eligible queued or in-progress runs.
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 queued or running jobs can clutter your repository and make it harder to spot the work that needs attention.
- Clear eligible runs without opening GitHub to review them one by one.
- Apply a staleness rule you describe in plain language.
- Receive a report showing what the automation did.
Setup
Build it in a few focused steps.
- 1Connect Celigo and GitHub once in the Notis portal.
- 2Create an automation in Automations, then New Automation, and give it a name.
- 3Describe which queued or in-progress runs to cancel and the staleness rule to use in one instruction.
- 4Choose a recurring schedule and where run reports should go.
- 5Test with one real example and confirm the report.
Questions about this workflow
Can Notis tell how long a run has been stuck?
It can use run details returned by GitHub to assess a rule you describe. Specify what counts as stale, and test the rule with a real example.
Will every queued or running job be canceled?
No. Describe the conditions for cancellation in your instruction. The GitHub action only cancels runs that are in a cancellable state.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Celigo to GitHub. A trigger fires from one place; an action lands in another.
Celigo 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.
Celigo 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.