Automatically Clear GitHub Actions Caches When Releasing
Before shipping a release, your workflows should run fresh. When a deal hits release stage in Hubspot, Notis clears any outdated GitHub Actions caches so builds start clean.
Trigger
Deal Stage UpdatedTrigger
Deal Stage UpdatedTrigger
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
Cached data from old builds can make it into production. Manually clearing caches is tedious and often forgotten before releases.
- Releases build fresh without cached baggage
- No manual cache clearing steps before shipping
- Reduces mysterious build issues from old cache data
- Keeps deployment pipelines predictable and clean
Setup
Build it in a few focused steps.
- 1Connect Hubspot and GitHub to Notis.
- 2Ask Notis: 'When a deal reaches Release stage, clear all GitHub Actions caches in [repository].'
- 3Select Deal Stage Updated as your trigger with 'Release' as the stage.
- 4Choose your notification channel.
- 5Test by advancing a deal to Release and verifying GitHub Actions caches clear.
Questions about this workflow
Can I clear specific caches only?
Yes. You can specify cache keys, for example 'clear caches for build and node_modules, but keep credentials cache'.
What if there are no caches to clear?
Notis logs that no matching caches were found and continues safely.
Does this impact other workflows?
No, it only clears the specified caches. Other workflows continue normally, but they'll rebuild their caches on next run.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Hubspot to GitHub. A trigger fires from one place; an action lands in another.
Hubspot triggers
GitHub actions
Contact Created Trigger
Contact Created Trigger
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Deal Stage UpdatedTrigger
Deal Stage UpdatedTrigger
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.
Not just Hubspot and GitHub. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business GitHub.