Clear Stale GitHub Caches for Mintlify Documentation
A clean cache can remove an entire class of mysterious documentation build failures.
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
Cache-related build problems are difficult to remember, diagnose, and clean up consistently.
- Reduces recurring cache-related confusion.
- Prevents stale artifacts from crowding repository storage.
- Turns technical housekeeping into a lightweight routine.
Setup
Build it in a few focused steps.
- 1Connect Mintlify and GitHub to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to make it in plain language.
- 3Instruct Notis to clear the GitHub Actions cache for the repository when Mintlify maintenance criteria indicate stale documentation builds.
- 4Select a recurring schedule and a reporting channel.
- 5Test it against one known stale cache key.
Questions about this workflow
Can it target one cache key?
Yes. Include the repository and cache key criteria in the plain-language instruction.
Does clearing a missing cache fail?
The GitHub action succeeds even when no matching cache is found.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Mintlify to GitHub. A trigger fires from one place; an action lands in another.
Mintlify triggers
GitHub actions
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
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 Mintlify and GitHub. Any 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.