Skip to content

Bolder bigger headings #315

Bolder bigger headings

Bolder bigger headings #315

Triggered via pull request September 12, 2024 21:05
Status Success
Total duration 7m 54s
Artifacts 3

CI.yml

on: pull_request
Matrix: build PST docs
Matrix: run-pytest
a11y-tests (ubuntu-latest, 3.12)
3m 46s
a11y-tests (ubuntu-latest, 3.12)
lighthouse-audit
4m 10s
lighthouse-audit
profiling
29s
profiling
Check coverage
35s
Check coverage
Fit to window
Zoom out
Zoom in

Annotations

3 warnings and 10 notices
build PST docs (macos-latest, 3.12)
These files were overwritten during the `brew link` step:
run-pytest (macos-14, 3.10)
These files were overwritten during the `brew link` step:
run-pytest (macos-14, 3.12)
These files were overwritten during the `brew link` step:
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/1983/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/1983/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.2 KB
lighthouse-results
5.21 MB
python-coverage-comment-action
461 Bytes