New issue
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
Azure pipelines branch name with slashes #244
Comments
KagamiChan
changed the title
Azure pipelines wrong branch name issue
Azure pipelines branch name with slashes
Nov 3, 2019
tested with a fork and it runs I could file a PR if you think it is good |
Since this library doesn't seem to be supported anymore I fix a bunch of things on a fork if you want to check it out and are still pulling the library into your packages: https://github.com/jtwebman/coveralls-next I would be willing to pull the fix into my fork. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi I'm trying using coveralls with Azure pipelines. The problem I met is that if I have a slash in branch name, then the coveralls report will point to a wrong branch because in Azure pipelines,
Build.SourceBranchName
will only take the last part.I'm not sure if coveralls could accept a "full path" like
refs/heads/foo/bar
, if so we could useBuild.SourceBranch
insteadThe text was updated successfully, but these errors were encountered: