Explore >> Select a destination
|
You are here 
|
akashgoswami.dev | ||
| | | | |
til.simonwillison.net
|
|
| | | | | I decided to make a GitHub repository public today that had previously been private. Unfortunately the revision history of that repository included some secret values, one of which I could not figure out a way to revoke. | |
| | | | |
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. | |
| | | | |
ionathan.ch
|
|
| | | | | ||
| | | | |
darekkay.com
|
|
| | | Don't fear history-changing Git commands - embrace them instead. | ||
