/explore
|
You are here 
|
danielpietzsch.com | ||
| | | | |
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.owlcode.eu
|
|
| | | | | How to revert the first commit in a local gir repository | |
| | | | |
roneo.org
|
|
| | | | | How to use Gitlab Pages hosted by Riseup with Hugo. | |
| | | | |
sookocheff.com
|
|
| | | This is something I often do but rarely remember the steps for. This post is intended to serve as a reminder for me and anyone else having the same question: how to add an upstream remote git repository. Start by forking the repository you are contributing to and cloning that repository to your local file system. In this example, we will use the Elasticsearch repository and assume you have cloned it locally. | ||
