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
{{ message }}
Repository navigation
Issues sections should link to local file in your IDE at given commit with highlighted line(s) #745
Should we close #722? What happens in CI? Should the CVS server get considered in the desinge decision?
We don't print issues in the CLI output (it would be way too much info), so I don't see that there's anything to consider about CI.
CI jobs may produce the Markdown artifacts, but artifacts' content isn't viewable online anyway, you have to download the file and open it - probably in your IDE 😁 So local path links should still cover most use cases, I think.
Activity
matejchalk commentedon Jul 12, 2024
We don't print issues in the CLI output (it would be way too much info), so I don't see that there's anything to consider about CI.
CI jobs may produce the Markdown artifacts, but artifacts' content isn't viewable online anyway, you have to download the file and open it - probably in your IDE 😁 So local path links should still cover most use cases, I think.
BioPhoton commentedon Jul 12, 2024
The thought was driven by the fact that ppl could store the report in the repo or add it to a pr.
I started to elaborate it here #748