Closed harri-halttunen-aktia closed 2 years ago
Hey harri-halttunen-aktia!
Thank you for reporting this. Will look into it.
I'm currently working on a new version (8) that will change a bit how the gitorigin.path
token behaves. Does the token resolves in the added test here look like you expect?
The test almost looks like what is needed. I would use this URL as an additional test case:
ssh://git@git.company.com/project_x/test-repository.git
as it contains both, dash (-) and underscore (_) characters. Also, it has a subdomain (not that it necessarily matter).I've released a new version that should solve this problem. It will appear sometime soon™.
${gitorigin.path,n}
seems to fail whengit ls-remote --get-url
command returns URL like this:ssh://git@git.company.com/project_x/test-repository.git
${gitorigin.path,n}
returns 'invalid-index' no matter whatn
is.As a side note, my goal is to build a Git URL like this:
https://git.company.com/projects/project_x/repos/test-repository/commits/8477f804daea99e6738b14c7a95e080265412abe