We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
8
When a git repo is hosted in Azure DevOps, the HttpsUrl does not contain .git suffix.
.git
The code in GitRepository is wrong, as it is hardcoded to expect the .git instead of reading origin from the git configuration
GitRepository
nuke/source/Nuke.Build/VCS/GitRepository.cs
Line 260 in 4bfee84
Use a Azure DevOps repo
the url will be HTTPS: https://Tenant@dev.azure.com/Tenant/TheProject/_git/this-is-my-repo SSH: git@ssh.dev.azure.com:v3/Tenant/TheProject/this-is-my-repo
GitRepository.HttpsUrl should return "https://Tenant@dev.azure.com/Tenant/TheProject/_git/this-is-my-repo"
GitRepository.HttpsUrl
GitRepository.HttpsUrl actually return "https://dev.azure.com/Tenant/TheProject/_git/this-is-my-repo.git"
No response
Yes
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Usage Information
8
Description
When a git repo is hosted in Azure DevOps, the HttpsUrl does not contain
.git
suffix.The code in
GitRepository
is wrong, as it is hardcoded to expect the.git
instead of reading origin from the git configurationnuke/source/Nuke.Build/VCS/GitRepository.cs
Line 260 in 4bfee84
Reproduction Steps
Use a Azure DevOps repo
the url will be
HTTPS: https://Tenant@dev.azure.com/Tenant/TheProject/_git/this-is-my-repo
SSH: git@ssh.dev.azure.com:v3/Tenant/TheProject/this-is-my-repo
Expected Behavior
GitRepository.HttpsUrl
should return "https://Tenant@dev.azure.com/Tenant/TheProject/_git/this-is-my-repo"Actual Behavior
GitRepository.HttpsUrl
actually return "https://dev.azure.com/Tenant/TheProject/_git/this-is-my-repo.git"Regression?
No response
Known Workarounds
No response
Could you help with a pull-request?
Yes
The text was updated successfully, but these errors were encountered: