Clear a known stale build cache for an assessment project
When you have identified a stale or corrupted cache, clear that exact key from the specified repository on a planned schedule.
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
A known bad cache can keep slowing project work until someone remembers to remove it.
- Remove a cache matching a specific key and optional ref.
- Automate a cleanup that has already been identified as necessary.
- Keep the repository and cleanup result in the run report.
Setup
Build it in a few focused steps.
- 1Connect Classmarker and GitHub once in Notis.
- 2Create an automation that clears only the cache key and optional ref provided for the specified repository.
- 3Pick a Notis cron schedule and choose a report destination.
- 4Test with one known stale cache key.
Questions about this workflow
Does this find stale caches automatically?
No. Provide the exact cache key and optional ref to clear. The action deletes matching caches and succeeds even if none are found.
Can I run this immediately after an assessment review?
The allowed trigger choices are a Notis webhook or cron schedule. This package uses a schedule; a webhook could be used for a request-driven cleanup instead.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Classmarker to GitHub. A trigger fires from one place; an action lands in another.
Classmarker 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.
Classmarker 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.