Clear a problematic GitHub Actions cache with incident context
Give Notis the affected repository and cache key, then let it clear the cache when incident follow-up calls for it.
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 or corrupted build caches can prolong incident recovery when cleanup requires a separate manual GitHub step.
- Reduce manual cache cleanup work
- Target a cache key tied to incident evidence
- Include cache cleanup in scheduled incident follow-up
Setup
Build it in a few focused steps.
- 1Connect Better Stack and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name and prompt.
- 3Tell Notis to clear the specified repository cache key only when the supplied incident context calls for cache cleanup.
- 4Choose a recurring schedule and where run reports should go.
- 5Test with one real repository and cache key, then review the run report.
Questions about this workflow
Does Better Stack provide the cache key automatically?
No source trigger event is available here. Make sure the repository, cache key, and reason for cleanup are supplied to Notis.
What happens if the cache key is not present?
The GitHub action succeeds even when it finds no matching caches to delete.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Better stack to GitHub. A trigger fires from one place; an action lands in another.
Better stack 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.
Better stack 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.