Any git gc related commands will not work on repositories that have had PRs or TAGs on github (merged or not)

[ykla]

Select Topic Area

Bug

Body

It is necessary to note that the project will not be affected by any actions taken via the bfg-repo-cleaner repository on GitHub, provided that the project in question has any PRs or TAGs that exist on GitHub. Please also refer to the following link: rtyley/bfg-repo-cleaner#516.

In the event that only the PRs are closed, rather than merged, I have not yet conducted the requisite tests. However, I have both closed and merged PRs, and I am the sole author of all submitted PRs. Furthermore, I am the sole proprietor of the entire project.

In point of fact, the title is accurate. As long as the project in question exists on GitHub and has any PR or tag, it is not possible to perform any GC operations nor are any -mirror-related operations permitted. It is possible that this is a design issue with GitHub.

I have attempted to contact GitHub's customer service, and both their automated and human representatives have asserted that the deletion of PRs with sensitive data is the only permitted reason. They have also requested that I identify the specific data that is considered sensitive.

Furthermore, even in the absence of the aforementioned script, simple Git garbage collection operations are ineffective, resulting in the generation of fake pushes akin to those described in the aforementioned article. Upon cloning the repository again, it becomes evident that the operation is ineffective.

I have attempted to implement the majority of the solutions proposed in the other issues, yet none of them have yielded the desired results.

This list is not exhaustive and includes, but is not limited to, the following resources:

• https://some-natalie.dev/blog/omit-PRs-clean-BFG

It should first be noted that as long as a Git repository on GitHub has been accessed via the PR (Pull Request) interface on GitHub, and as long as there is an existing PR on the GitHub webpage (regardless of whether its status is merged, closed, or in progress), no operations can be performed on the Git data of the repository. This is because any modifications made to the Git information will have no effect, as the repository on GitHub will always remain unchanged.
It is generally accepted that people need to modify Git information in the following situations:

1. Binary files, such as videos, were erroneously incorporated into the Git project.
2. It concerns confidential or private information.
3. There is a necessity to modify multiple Git-related items in a single operation, such as emails and commit authors.

However, GitHub support will only assist in deleting PRs in the second case. This effectively prevents any Git operations such as git gc or git push that modify Git information from being performed on the repository on GitHub. In other words, Git projects on GitHub are unable to perform any gc operations unless the project has only one participant who always makes direct commits without using any PRs. The same applies to the existence of tags in git repositories, but one can remove them on one's own.