GIT

Problèmes déjà rencontrés

Filename too long

Problem

The limitation to 260 chars in a path it's a general Windows API imitation

Solution

solution possible, rend fonctionnel le repo

git config --system core.longpaths true

Generated build files

Problem

A build script or any other execution type generated multiples new build, caches or non sources files. Theses files can be numerous and take huge amount of hard disk space, that will impact git performance. If they are not one time generated unique files but generated for each new local execution, the git workflow will be also poluted by numerous irrelevant files in each new commit.

Solution

I would recommend removing the files from the git repository using git rm {file} and then add that file to .gitignore. From then on, you should only commit the changes to the files that you actually touched, and don't track the autogenerated files in git anymore.


Children
  1. GitHub
  2. GitLab
  3. Hook
  4. Workflow

Backlinks