[Feature Request] Ability to delete commits (because sensitive information) #5089

New Issue

GiteaMirror · 2025-11-02T06:14:04-06:00

GiteaMirror commented

2025-11-02 06:14:04 -06:00

Originally created by @ghost on GitHub (Mar 20, 2020).

Sometimes it happens that you accidentally push some sensitive information to your git repository, like passwords or real name, etc.

On GitHub you can contact the support team and they can help you in deleting these private information and keep it without traces (it doesn't appear in commit history).

I suggest there should be a feature in Gitea so that an admin user can delete commits from both the Gitea database and the Git repository in the file system, meaning it would be just like if the commit wouldn't ever have been pushed in the first place.

Citation needed: Should the repository owner themselves be able to delete the commits?

Additionally, pull requests should also be deleteable.

Originally created by @ghost on GitHub (Mar 20, 2020). Sometimes it happens that you accidentally push some sensitive information to your git repository, like passwords or real name, etc. On GitHub you can contact the support team and they can help you in deleting these private information and keep it without traces (it doesn't appear in commit history). I suggest there should be a feature in Gitea so that an admin user can delete commits from both the Gitea database and the Git repository in the file system, meaning it would be just like if the commit wouldn't ever have been pushed in the first place. Citation needed: Should the repository owner themselves be able to delete the commits? Additionally, pull requests should also be deleteable.

GiteaMirror added the issue/stale label 2025-11-02 06:14:04 -06:00

GiteaMirror closed this issue

2025-11-02 06:14:04 -06:00

GiteaMirror commented

2025-11-02 06:14:04 -06:00

@lafriks commented on GitHub (Mar 20, 2020):

Most of the actions should be done by rewriting git history on client and then force pushing, same with PR

@lafriks commented on GitHub (Mar 20, 2020): Most of the actions should be done by rewriting git history on client and then force pushing, same with PR

GiteaMirror commented

2025-11-02 06:14:05 -06:00

@stale[bot] commented on GitHub (May 19, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (May 19, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented

2025-11-02 06:14:05 -06:00

@stale[bot] commented on GitHub (Jun 3, 2020):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Jun 3, 2020): This issue has been automatically closed because of inactivity. You can re-open it if needed.

GiteaMirror referenced this issue

2025-11-02 14:36:22 -06:00

[PR #5089] [MERGED] ZH-CN translation of Installation part #17631

Sign in to join this conversation.