Clear a known stale cache for transaction tooling
When a transaction tooling change leaves a specific Actions cache unusable, clear that cache key without a manual repository detour.
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
An outdated or corrupted build cache can slow down transaction tooling work until someone remembers to remove it.
- Remove a specified cache when there is a clear reason to do so.
- Reduce manual repository maintenance steps.
- Keep cache cleanup tied to transaction tooling review.
Setup
Build it in a few focused steps.
- 1Connect Blocknative and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for transaction tooling cache review.
- 3In one instruction, tell Notis to clear the supplied repository cache key only when the review identifies it as outdated or corrupted, including the supplied ref when relevant.
- 4Choose a recurring schedule and select where run reports should go.
- 5Test with one real repository, cache key, and optional ref.
Questions about this workflow
Can this discover every stale cache automatically?
The listed action deletes caches by a specific key and optional ref. Supply those details and a reason to clear them.
What if no cache matches the key?
The action succeeds even when it finds no matching cache to delete.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Blocknative to GitHub. A trigger fires from one place; an action lands in another.
Blocknative 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.
Blocknative 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.