Closed Bolero-fk closed 1 year ago
Thanks for the detailed report. We're looking into a fix for this. Will notify you when it's been released.
This should be fixed now @Bolero-fk Related release: https://github.com/insightsengineering/coverage-action/releases/tag/v2.4.1
What happened?
The issue arises when a branch name includes URL-unsafe characters, such as the hashtag (
#
). In these cases, the badge fails to display properly.Steps to Reproduce:
AddNewFeature#1
).coverage-action
workflowAdditional Information: I was able to display the badge correctly by manually changing the URL to encode the '#' character. For example, changing the URL from this:
![badge](<RepositoryName>/_xml_coverage_reports/data/AddNewFeature#1/badge.svg)
To this:![badge](<RepositoryName>/_xml_coverage_reports/data/AddNewFeature%231/badge.svg)
This modification allowed the badge to be displayed as intended.Relevant log output
No response
Code of Conduct
Contribution Guidelines
Security Policy