joaorb64 / joaorb64/TournamentStreamHelper
Clean up the repository
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 139
- Forks
- 59
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 6
Description
I am trying not to be too harsh.
This repository is very badly organized. Not just are there a bunch of assets in the git history (including deleted stuff), but also every release has a TSH.exe in the git history. This is not just bad practice and unnecessary and unhelpful due to binaries having basically unusable change histories, but it bloats up the whole repository. Cloning the repository takes 10 minutes and takes up 5GB compressed and 50GB uncompressed!
This is highly impractical for developing and releasing. I would highly recommend and greatly appreciate squashing the history without assets, or at least without TSH.exe, and include them as proper assets in a GitHub release.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by auditing the Git history for assets and recurring TSH.exe binaries, then review how GitHub release assets are handled; done means the repository history is reduced without those binaries and releases provide the needed assets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- devops, release
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100