[Feature Request] Ability to Delete Gitea Actions Runs at the Repository Level #14678

New Issue

GiteaMirror · 2025-11-02T11:19:47-06:00

GiteaMirror commented

2025-11-02 11:19:47 -06:00

Originally created by @ZPascal on GitHub (Jun 30, 2025).

Feature Description

Summary

Currently, Gitea does not offer a way to delete past Actions workflow runs at the repository level. Once a workflow has run, it remains listed indefinitely, with no user interface or API support to remove it. This can lead to clutter, storage concerns, and issues with data retention policies.

Why is this needed

Repository cleanup: Over time, workflow history grows and becomes difficult to manage.
Privacy/Security: Some workflow runs may contain sensitive data (e.g., environment variables in logs) and should be deletable.
Compliance: Organizations may require cleanup mechanisms for audit or retention purposes.
Debugging: Failed or test runs may pollute the run history during development.

Proposed Solution

Introduce support for deleting individual or bulk Gitea Actions runs, with options such as:

UI Option: "Delete Run" button in the Actions tab next to each run.
Bulk deletion: Ability to delete multiple runs at once (e.g., delete all failed runs or older than X days).
API support: Allow deletion via Gitea REST API for automation.
Permissions check: Only users with appropriate rights (e.g., repo admin) should be able to delete runs.

Benefits

Better repository hygiene
Reduces clutter in the Actions tab
Frees up storage space on self-hosted instances
Helps organizations comply with internal policies

Current Workarounds

None available. Runs are retained indefinitely with no manual deletion option through the UI or API.

Improves Gitea Actions usability and manageability
Aligns with GitHub/GitLab CI capabilities, which both allow workflow run deletion

Screenshots

No response

Originally created by @ZPascal on GitHub (Jun 30, 2025). ### Feature Description ## Summary Currently, Gitea does not offer a way to delete past Actions workflow runs at the repository level. Once a workflow has run, it remains listed indefinitely, with no user interface or API support to remove it. This can lead to clutter, storage concerns, and issues with data retention policies. ## Why is this needed - **Repository cleanup:** Over time, workflow history grows and becomes difficult to manage. - **Privacy/Security:** Some workflow runs may contain sensitive data (e.g., environment variables in logs) and should be deletable. - **Compliance:** Organizations may require cleanup mechanisms for audit or retention purposes. - **Debugging:** Failed or test runs may pollute the run history during development. ## Proposed Solution Introduce support for deleting individual or bulk Gitea Actions runs, with options such as: - **UI Option:** "Delete Run" button in the Actions tab next to each run. - **Bulk deletion:** Ability to delete multiple runs at once (e.g., delete all failed runs or older than X days). - **API support:** Allow deletion via Gitea REST API for automation. - **Permissions check:** Only users with appropriate rights (e.g., repo admin) should be able to delete runs. ## Benefits - Better repository hygiene - Reduces clutter in the Actions tab - Frees up storage space on self-hosted instances - Helps organizations comply with internal policies ## Current Workarounds None available. Runs are retained indefinitely with no manual deletion option through the UI or API. ## Related - Improves Gitea Actions usability and manageability - Aligns with GitHub/GitLab CI capabilities, which both allow workflow run deletion ### Screenshots _No response_

GiteaMirror added the type/proposal label 2025-11-02 11:19:47 -06:00

GiteaMirror closed this issue

2025-11-02 11:19:47 -06:00

GiteaMirror commented

2025-11-02 11:19:47 -06:00

@TheFox0x7 commented on GitHub (Jun 30, 2025):

Isn't this a dupe of https://github.com/go-gitea/gitea/issues/26219?

@TheFox0x7 commented on GitHub (Jun 30, 2025): Isn't this a dupe of https://github.com/go-gitea/gitea/issues/26219?

GiteaMirror commented

2025-11-02 11:19:48 -06:00

@ZPascal commented on GitHub (Jun 30, 2025):

Thank you @TheFox0x7 for the information. I'll close the case. The feature will be delivered with version 1.25.0.

@ZPascal commented on GitHub (Jun 30, 2025): Thank you @TheFox0x7 for the information. I'll close the case. The feature will be delivered with version 1.25.0.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#14678