Respond to confirmed cache failures across Appcircle and GitHub
When Appcircle logs point to a stale or corrupted GitHub Actions cache, Notis can clear the key you identify.
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 suspected cache problem can keep wasting build time when clearing the relevant cache requires a separate manual step.
- Connects build evidence to a targeted cache cleanup
- Can clear a specific cache key and optional ref
- Reduces manual cleanup during build troubleshooting
Setup
Build it in a few focused steps.
- 1Connect Appcircle and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to inspect recent Appcircle logs and clear only the specified GitHub Actions cache key and optional ref when the evidence confirms a cache issue.
- 4Pick a recurring schedule and choose where run reports go.
- 5Test with one real cache-related failure and verify the intended cache was cleared.
Questions about this workflow
Can it clear every cache in a repository?
This action clears caches matching a specified key and optional ref. Include the intended key in your instruction.
What if the logs do not confirm a cache issue?
Tell Notis to report the evidence and take no cache action when the cause is uncertain.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Appcircle to GitHub. A trigger fires from one place; an action lands in another.
Appcircle 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.
Appcircle 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.