You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In one of my projects, I am getting problems with branch names that are too long.
Unfortunately, this is something not within my reach to force users to make branch names with smaller lengths.
I was able to workaround with setting git configuration globally with "longpaths = true", but I don't like this solution, as it is a global setting, and could affect other repositories.
git config --global core.longpaths true
I tried a local repository setting git config core.longpaths true but peru obviously is not following the local repo configuraiton, only global.
I tried to manually change the git configuration for the repository inside the peru cache folder, and this works.
So, maybe we could have an extra configuration for this?
Any ideas on how to solve this?
Regards,
The text was updated successfully, but these errors were encountered:
Hi,
In one of my projects, I am getting problems with branch names that are too long.
Unfortunately, this is something not within my reach to force users to make branch names with smaller lengths.
I was able to workaround with setting git configuration globally with "longpaths = true", but I don't like this solution, as it is a global setting, and could affect other repositories.
git config --global core.longpaths true
I tried a local repository setting
git config core.longpaths true
but peru obviously is not following the local repo configuraiton, only global.I tried to manually change the git configuration for the repository inside the peru cache folder, and this works.
So, maybe we could have an extra configuration for this?
Any ideas on how to solve this?
Regards,
The text was updated successfully, but these errors were encountered: