We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
For files-at-rest, it would be nice if we could show inline annotations for findings, a la CodeQL, etc.
Investigate whether this already works. We could try this with e.g. pytest-github-actions-annotate-failures.
pytest-github-actions-annotate-failures
If it Just Works, add it to the documentation.
If it doesn't, investigate how to make it work with existing tools.
If that doesn't work, try to figure out how to generate appropriate output for GitHub/Lab.
As a bonus, it would be lovely to also get "sourcemaps," for built content... but that's... really hard.
c/f jupyter/accessibility#139 (comment)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Problem
For files-at-rest, it would be nice if we could show inline annotations for findings, a la CodeQL, etc.
Proposed Solution
Investigate whether this already works. We could try this with e.g.
pytest-github-actions-annotate-failures
.If it Just Works, add it to the documentation.
If it doesn't, investigate how to make it work with existing tools.
If that doesn't work, try to figure out how to generate appropriate output for GitHub/Lab.
As a bonus, it would be lovely to also get "sourcemaps," for built content... but that's... really hard.
Additional context
c/f jupyter/accessibility#139 (comment)
The text was updated successfully, but these errors were encountered: