For clarification, the commit has checked in sources, which is the reason for deletion.

Also you can keep the fields unfilled if you do not have a real timeline (point 3 is not limited in your case)

Noted, thanks.

Hello. :wave:
I'm currently trying to find out more information about the policy regarding commit deletion, I would ask for a bit of patience. Thank you.

Hi there, thanks for responding! Yes, I can wait for an update on this.

Hello, sorry for the delay, Fedora infra underwent a data center move last week.

I did some digging and, as I suspected, the policy for commit deletion is rather strict.

Let me bring this up again during today's releng weekly and get back to you with a definitive answer.

I brought it up during releng weekly, logs can be found here [1].

The agreed upon policy [2] states:
AGREED: Move branches with huge commits to refs/archive/ and create new sanitized branches (+6, 0, 0)

The commit can hardly be described as "huge" so we agreed that it would be best if, in this specific case, you went ahead and reverted the commit.

Apologies for not being able to help you more.

[1] https://meetbot.fedoraproject.org/meeting-3_matrix_fedoraproject-org/2025-07-07/releng.2025-07-07-14.59.log.html
[2] https://pagure.io/releng/issue/7265

The commit can hardly be described as "huge" so we agreed that it would be best if, in this specific case, you went ahead and reverted the commit.

Uhh no? That doesn't help because a tarball was checked into the tree.

it means checkouts will be ~467kb bigger. Is 475k really a issue these days?

Git is kind of crappy with binary downloads, so yeah.

So, should I revert the commit or wait for it to be deleted?

I think you can just revert it/push a commit removing it. Sure, new git clones will be larger than they need to be because that thing is in history, but it's only 475k...