Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

clean up repo #4

Open
Remi-Gau opened this issue Nov 8, 2023 · 6 comments
Open

clean up repo #4

Remi-Gau opened this issue Nov 8, 2023 · 6 comments

Comments

@Remi-Gau
Copy link
Contributor

Remi-Gau commented Nov 8, 2023

not very urgent but this repo is getting kind of big and this may come back to bite us if we need to do any operation on it at some point

suggestion : squash commits in between release and purge the history

@Remi-Gau
Copy link
Contributor Author

Remi-Gau commented Nov 8, 2023

@ymzayek @bthirion

@ymzayek
Copy link
Member

ymzayek commented Nov 8, 2023

Agreed

@bthirion
Copy link
Member

bthirion commented Nov 8, 2023

Sorry, but what is the risk ?

@Remi-Gau
Copy link
Contributor Author

Remi-Gau commented Nov 8, 2023

not very high except that some operations that should be fast (clone, fetch) are very slow on the repo already and they may get to a point where they are so slow they prevent us from working on it

@AlexandreAbraham
Copy link

Whether you clean it or not, do not hesitate to use partial clone. Blobless and treeless clones can save you juge amounts of time. Basically, these clones download part of the history but not all the diffs. Those diffs are accessed only when needed.

@Remi-Gau
Copy link
Contributor Author

Remi-Gau commented Nov 8, 2023

I agree but that's when you need to those diffs that things may get sluggish. So it is definitely just a once in a blue moon use case (only discovered it when wanting to check what a page of the doc looked like in previous versions) but for long term maintenance it may be better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants