Clear stale build cache after a release
When a Beamer update makes a build cache outdated, have Notis clear the specified GitHub Actions cache key.
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
Release related cache cleanup is easy to forget, especially when the reason for clearing it is buried in changelog activity.
- Connects a release decision to the cache cleanup it requires.
- Avoids repeated manual cache maintenance.
- Keeps the cleanup condition and cache key in a plain language instruction.
Setup
Build it in a few focused steps.
- 1Connect Beamer and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3In one instruction, ask Notis to review Beamer changelog activity and clear the named GitHub Actions cache key only when the release notes indicate it is stale; include the repository and optional ref.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real release note and the cache key you intend to clear.
Questions about this workflow
Does every Beamer update clear the cache?
No. State the release condition in your instruction and identify the cache key to clear. The GitHub action deletes caches matching the specified key and optional ref.
Can Notis infer the cache key from a release announcement?
Only if that information is present in the Beamer activity. Otherwise include the key and repository in your instruction.
What if no matching cache exists?
The GitHub action succeeds even when it finds no matching cache to delete, and the run report can show what happened.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Beamer to GitHub. A trigger fires from one place; an action lands in another.
Beamer 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.
Beamer 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.