Keep GitHub Actions cache cleanup on track
Set the cache key, optional ref, and criteria that define stale entries, then let Notis handle the recurring cleanup.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Clear repository cache by key
Deletes github actions caches from a repository matching a specific `key` and an optional git `ref`, used to manage storage or clear outdated/corrupted caches; the action succeeds even if no matching caches are found to delete.
Why this helps
Old cache entries are easy to forget when cleanup is an occasional task competing with active development work.
- Make cache cleanup part of routine repository maintenance.
- Target the cache key and optional ref you specify.
- Avoid spending time searching for matching entries manually.
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 your cache key, optional ref, and criteria for stale entries 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 decide that a cache is stale on its own?
Provide a cleanup rule and the key and optional ref to target. If your rule needs history or a baseline not available to Notis, include it in the instruction or request context.
Does the cleanup fail if the cache is already gone?
The GitHub action succeeds even when no matching caches are found.
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.