Question regarding artifact retention policies in Gitea Actions

Hi everyone,

I am currently in the process of migrating a few workflows from GitLab CI to Gitea Actions, and I have a question regarding storage management.

We are running Gitea via Docker Compose. I’ve successfully set up act_runner, and the builds are triggering correctly. However, I want to configure a retention policy for the build artifacts (binaries and logs) to prevent them from filling up our storage volume over time.

In GitLab, we used expire_in. Is there a direct equivalent in the Gitea Actions workflow YAML, or should this be handled via a cron job/cleanup script on the server side?

Here is a snippet of the current step I’m using to upload the artifact:

- name: Upload build artifact
  uses: actions/upload-artifact@v3
  with:
    name: release-build
    path: ./dist/
    # Is there a retention parameter here compatible with Gitea?

Any advice on best practices for keeping the artifact storage clean would be appreciated.

Thanks!

Asking myself the same question. Did you find out more?