Clear stale build caches on a schedule
Keep wasteful leftovers from quietly consuming resources and mental bandwidth.
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 caches accumulate because cleanup is useful but never feels urgent enough to remember.
- Reduces stale CI storage
- Makes maintenance predictable
Setup
Build it in a few focused steps.
- 1Connect both integrations to Notis once.
- 2Create a new portal automation.
- 3Write that each week Notis should review Corrently conditions and clear the named obsolete GitHub Actions cache key when cleanup is appropriate.
- 4Choose a weekly schedule and report channel, then test with a disposable cache key.
Questions about this workflow
Do I configure cache fields?
No. Include the repository and cache key in your instruction and Notis applies it.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Corrently to GitHub. A trigger fires from one place; an action lands in another.
Corrently 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 Corrently and GitHub. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business GitHub.