Skip to content
Notis

Clear GitHub Actions caches on a weekly schedule

Stale build caches pile up until CI gets flaky, and pruning them is a chore you never quite get to. Notis clears the GitHub Actions caches matching your key on a weekly schedule so storage stays lean and builds stay honest.

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

Old GitHub Actions caches accumulate and cause flaky or slow builds, but clearing them manually is a task that never reaches the top of the list.

  • CI storage stays lean without a manual pruning chore
  • Fewer flaky builds caused by outdated cached artifacts
  • A predictable weekly cleanup you never have to remember

Setup

Build it in a few focused steps.

  • 1Connect GitHub to Notis one time in the portal.
  • 2Open Automations in the portal and choose New Automation.
  • 3Write it plainly: every week, clear the GitHub Actions caches matching my key on the repository.
  • 4Pick a recurring weekly schedule as the trigger and choose a channel for run reports.
  • 5Run the automation once to confirm the cache cleanup completes.

Questions about this workflow

What if there are no matching caches?

The action succeeds even when no caches match the key, so the run never fails on an empty result.

Can I limit it to a git ref?

Yes. Your instruction can name an optional ref alongside the key.

Does this need a Jira event?

No. It runs on a recurring schedule, aligned with your weekly cleanup rhythm.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Jira to GitHub. A trigger fires from one place; an action lands in another.

Jira triggers

GitHub actions

New Issue

Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.

TriggerInstant

Accept a repository invitation

Accepts a pending repository invitation that has been issued to the authenticated user.

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

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.

ActionInstant

Updated Issue

Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.

TriggerInstant

List stargazers

Deprecated: lists users who have starred a repository; use `list stargazers` instead.

ActionInstant

Star a repository for the authenticated user

Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.

ActionInstant

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.

ActionInstant

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.

ActionInstant

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.

ActionInstant

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.

ActionInstant

Connect any two apps with Notis in the middle.

Not just Jira 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.