Tag Archives: practices

However, if you are going to use git-filter-department, make sure you finish your command with ` –tag-name-filter cat – –all` unless you might be actually really sure you know what you’re doing. Support for large repositories is an active git matter, so look ahead to adjustments. Remember that not everyone may be utilizing the same memory configuration you might be. Support for large information is an active git matter, so watch for modifications. Yes it can be accomplished in a sufficiently easy/non-critical surroundings with something like Abhijit Menon-Sen’s document on […]

Don’t be afraid of “/” within the department name when acceptable (but do be afraid of using a remote’s name as a listing component of a department name, or correspondingly naming a remote after a branch name or directory component). Yes, of course git lets you rewrite public history, but it’s problematic for everyone and thus it is just not best follow to do so. Once you git push your changes to the authoritative upstream repository or in any other case make the commits or tags publicly visible, you should […]