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
The Git class currently has a hard-coded configuration for replacing URL prefixes, which is limited to replacing the prefix git:// by https://.
In our environment, there was the need to replace a URL like "git@github.com:" (used as a submodule reference and interpreted as SSH) by the URL "https://github.com/". I assume that such replacements cannot be done by ORT in a generic way, since the prefix to be replaced contains a domain; from my research, I found that Git currently does not support wildcards in its prefix mappings. So, it would be nice if there was a straight-forward way to modify the replacement configuration used by Git.
Since version control systems are implemented as plugins, would it make sense to support a similar configuration mechanism as for other types of plugins? Via this mechanism, other hard-coded settings (for instance the history depth) could be made configurable as well.
The text was updated successfully, but these errors were encountered:
@sschuberth, thank you for pointing this out. Yes, there is at least a very strong relation between these issues, the same use cases are addressed. Not sure whether the aspect of making the VCS provider itself configurable is new though; the referenced issue seems to focus more on other strategies.
The
Git
class currently has a hard-coded configuration for replacing URL prefixes, which is limited to replacing the prefixgit://
byhttps://
.In our environment, there was the need to replace a URL like "git@github.com:" (used as a submodule reference and interpreted as SSH) by the URL "https://github.com/". I assume that such replacements cannot be done by ORT in a generic way, since the prefix to be replaced contains a domain; from my research, I found that Git currently does not support wildcards in its prefix mappings. So, it would be nice if there was a straight-forward way to modify the replacement configuration used by
Git
.Since version control systems are implemented as plugins, would it make sense to support a similar configuration mechanism as for other types of plugins? Via this mechanism, other hard-coded settings (for instance the history depth) could be made configurable as well.
The text was updated successfully, but these errors were encountered: