Clear cache clutter before it slows you down
Cache problems are annoying precisely because they appear at the wrong moment. A recurring cleanup rule can remove known bad state before it becomes a distraction.
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
Stale caches can cause confusing failures and force founders into repeated debugging detours.
- Reduces recurring cache-related confusion
- Keeps cleanup tied to a clear rule
- Cuts emergency debugging interruptions
Setup
Build it in a few focused steps.
- 1Connect Rosette text analytics and GitHub to Notis once in the portal.
- 2Create a scheduled automation in the portal or ask Notis to maintain known problematic cache keys.
- 3Use this instruction: Analyze the supplied maintenance notes and clear only the GitHub Actions cache keys explicitly identified as stale or corrupted.
- 4Pick a weekly schedule, choose a run-report channel, and test with one known-safe cache key.
Questions about this workflow
Does it delete source code?
No. This action clears matching GitHub Actions caches in the repository.
Can it clear every cache?
The safer pattern is to name explicit keys or refs in the plain-language instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Rosette text analytics to GitHub. A trigger fires from one place; an action lands in another.
Rosette text analytics 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.
Rosette text analytics 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.