Refresh GitHub build caches after gallery changes
When a Cincopa gallery update makes a repository cache stale, Notis can clear the cache by its supplied key.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
Outdated cached media can make a build or publishing workflow keep using the wrong gallery assets.
- Target outdated cache entries by key
- Reduce manual cache cleanup
- Help builds pick up current gallery assets
Setup
Build it in a few focused steps.
- 1Connect Cincopa and GitHub once in Notis.
- 2Create an automation in the portal or tell Notis to create one in plain language.
- 3Ask Notis to clear the specified GitHub Actions cache only when a gallery update report identifies a stale or corrupted cache key.
- 4Choose the Notis webhook trigger and configure the sender to make an HTTP request to it.
- 5Choose a report channel and test with one real gallery update and an identified cache key.
Questions about this workflow
Does this clear all repository caches?
No. The action targets a cache by key and can optionally use a Git reference. Include the correct key in the report or instruction.
What if no cache matches the key?
GitHub reports success even when there is no matching cache to delete.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Cincopa to GitHub. A trigger fires from one place; an action lands in another.
Cincopa 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.
Cincopa 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.