repository name must be lowercase #3151
-
I'm trying to work out if this error is being handled correctly. Despite my advice, the Azure DevOps project I'm working on contains spaces and upper-case characters, as does its main repo. So do many more in our tenant. For this particular example I've managed to successfully switch to lowercase without affecting the remote. However, removing spaces will also affect the remote which ideally I'd like to avoid due to the number of staff affected. Is there a simple way to escape the spaces/non docked friendly characters? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 6 replies
-
In which use case do you see such error ? :) |
Beta Was this translation helpful? Give feedback.
-
Maybe |
Beta Was this translation helpful? Give feedback.
@nvuillam
results of further testing
Spaces/special characters in Azure DevOps project names and/or repo names do cause issues.
However, this is a docker limitation and not an issue with Megalinter itself. Docker complained further about the use of quotes in an Azure DevOps pipeline.
Solutions
The best solution in my opinion - avoid naming projects or repositories with special characters other than . - or _
alternatively - make use of pipeline variables to manipulate unsupported characters. However, this will affect the use of the pull request commenter.