Skip to content

Use a different CSS class to mark TOC levels as visible #770

Use a different CSS class to mark TOC levels as visible

Use a different CSS class to mark TOC levels as visible #770

Triggered via pull request March 11, 2025 19:55
Status Success
Total duration 4m 7s
Artifacts 2

CI.yml

on: pull_request
Matrix: run-pytest
Check coverage
37s
Check coverage
profiling
26s
profiling
coverage-comment  /  Display code coverage
0s
coverage-comment / Display code coverage
Fit to window
Zoom out
Zoom in

Annotations

10 notices
Check coverage
Starting action
Check coverage
HTTP Request: GET https://api.github.com/repos/pydata/pydata-sphinx-theme "HTTP/1.1 200 OK"
Check coverage
Generating comment for PR
Check coverage
HTTP Request: GET https://api.github.com/repos/pydata/pydata-sphinx-theme/contents/data.json?ref=python-coverage-comment-action-data "HTTP/1.1 200 OK"
Check coverage
HTTP Request: GET https://api.github.com/user "HTTP/1.1 403 Forbidden"
Check coverage
HTTP Request: GET https://api.github.com/repos/pydata/pydata-sphinx-theme/issues/2163/comments "HTTP/1.1 200 OK"
Check coverage
Adding new comment
Check coverage
HTTP Request: POST https://api.github.com/repos/pydata/pydata-sphinx-theme/issues/2163/comments "HTTP/1.1 403 Forbidden"
Check coverage
Cannot post comment. This is probably because this is an external PR, so it's expected. Ensure you have an additional `workflow_run` step configured as explained in the documentation (or alternatively, give up on PR comments for external PRs).
Check coverage
Ending action

Artifacts

Produced during runtime
Name Size
coverage-data-3.12
16.4 KB
python-coverage-comment-action
1.3 KB