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
Bug report feels strong. It's more that it works as intended but I'm wondering if the current behaviour is desirable. I'd want to be able to click links in error reports and use that as a way to test the links but the colon separator gets included in the link and thus the link doesn't work. Can we include parentheses around the link or a space before the colon?
Current Behavior
Clicking link in error messages might include the colon (:) which results in an invalid link.
Step to reproduce
To reproduce you need to include a link that gets reported as a broken link for example a link that has bot protection and gives a 403.
Broken link in /home/runner/work/c-git.github.io/c-git.github.io/content/rust/areweyet.md to https://wiki.mozilla.org/Areweyet: Client error status code (403 Forbidden) received
But in the GitHub action the clickable link includes the colon.
The text was updated successfully, but these errors were encountered:
Bug Report
Environment
Zola version: 0.19.2
ExpectedDesired BehaviorBug report feels strong. It's more that it works as intended but I'm wondering if the current behaviour is desirable. I'd want to be able to click links in error reports and use that as a way to test the links but the colon separator gets included in the link and thus the link doesn't work. Can we include parentheses around the link or a space before the colon?
Current Behavior
Clicking link in error messages might include the colon (:) which results in an invalid link.
Step to reproduce
To reproduce you need to include a link that gets reported as a broken link for example a link that has bot protection and gives a 403.
Example from the github action failure on my site below. It's parsed fine by GitHub Markdown
But in the GitHub action the clickable link includes the colon.
The text was updated successfully, but these errors were encountered: