What happens: When the url action input is provided with a trailing slash (e.g., url: https://example.github.io/myrepo/), entry.sh passes it verbatim to vitals.xsl. The XSL template constructs badge copy-to-clipboard Markdown as []({$url}/{$name}-vitals.html), producing a double slash in the path: [](https://example.github.io/myrepo//simple-vitals.html). Neither entry.sh nor vitals.xsl strips a trailing slash from the url parameter before concatenating the filename.
What should happen: The generated badge Markdown should contain valid single-slash paths regardless of whether the url input ends with a trailing slash. The entry.sh script should strip any trailing slash from url before passing it to the XSL transformation.
What happens: When the
urlaction input is provided with a trailing slash (e.g.,url: https://example.github.io/myrepo/),entry.shpasses it verbatim tovitals.xsl. The XSL template constructs badge copy-to-clipboard Markdown as[]({$url}/{$name}-vitals.html), producing a double slash in the path:[](https://example.github.io/myrepo//simple-vitals.html). Neitherentry.shnorvitals.xslstrips a trailing slash from theurlparameter before concatenating the filename.What should happen: The generated badge Markdown should contain valid single-slash paths regardless of whether the
urlinput ends with a trailing slash. Theentry.shscript should strip any trailing slash fromurlbefore passing it to the XSL transformation.