[#46684] - [5.4] Clean cache for merged PR
- Fixed in Code Base
- 21 Jan 2026
- Medium
- Build: 5.4-dev
- # 46684
- Diff
- rdeutz:add-clean-cache-workflow
User tests: Successful: Unsuccessful:
Summary of Changes
We are running out of disk space for the cache. This workflow cleans the cache for merged PR. This should free up enough space.
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | Repository |
I would also let GitHub do the job and not add an extra Workflow for it.
This PR appears in the Patch Tester list with the 5.4-dev filter. A bit confusing!
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/46684.
This PR appears in the Patch Tester list with the 5.4-dev filter. A bit confusing!
@ceford Why confusing? The PR is for the 5.4-dev Branch. What always can happen is that a PR changes only development files which are not part of an installed Joomla, and so the patchtester cannot find any changed files. That would also happen in a PR changes e.g. the "build/build.php" script.
| Labels |
Added:
PR-5.4-dev
|
||
| Title |
|
||||||
As discussed in today's maintainers meeting, we will merge this PR and watch how things go.
| Status | Pending | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2026-01-21 19:25:38 |
| Closed_By | ⇒ | richard67 |
It seems when we reach the limit, oldest caches are deleted anyway, so the limit won't be exceeded. See the message here https://github.com/joomla/joomla-cms/actions/caches :
So we don't really need a clean up action. However, it might be useful still.