Explore >> Select a destination
|
You are here 
|
ionathan.ch | ||
| | | | |
akashgoswami.dev
|
|
| | | | | A quick how to guide on how to remove data from a repository's history | |
| | | | |
cullmann.io
|
|
| | | | | Today I did run again into an old problem: You need to archive a lot small and large files inside a single Git repository and you have no support for Git LFS available. You did this several year and now you ended up in a state where cloning and working with the repository is unbearable slow. What now? Last time I did run into that, I archived the overfull repository to some "rest in peace" space and used git filter-branch to filter out no longer needed and too large objects from a repository copy that then will replace the old one for daily use. | |
| | | | |
www.babaei.net
|
|
| | | | | Host Unreal Engine 4 projects on Microsoft Azure DevOPS with unlimited cost free Git LFS quota UPDATE 1 [2021/07/25]: It seems that Git LFS is able to resume your pushes after a network failure. At least it's like that on Microsoft Azure DevOPS. So, it should be totally redundant to divide huge commits into smaller ones. How have I noticed this? Today, I pushed a huge single commit (around 53GBs) and it failed at 39GB due to a connection error without me noticing it for some time. A few hours later, when... | |
| | | | |
without.boats
|
|
| | | |||
