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
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 use Build.SourceBranch instead
The text was updated successfully, but these errors were encountered:
KagamiChan
changed the title
Azure pipelines wrong branch name issue
Azure pipelines branch name with slashes
Nov 3, 2019
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.
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: