PR - (#172) fix: typing-extensions dependency missing #319
pr.yml
on: pull_request
Discover minimum Python version
/
Discover minimum Python version
3s
Upload PR details to artifact
2s
Formatting and security
/
Verify code formatting and security
27s
Unit Tests
/
Verify unit tests are successful
34s
API documentation
/
Verify if generated API documentation is up to date
27s
Build Docker image
/
Build a Docker image
48s
Fetch the updated documentation
3s
Annotations
4 warnings and 10 notices
Unit Tests / Verify unit tests are successful
Starting action
|
Unit Tests / Verify unit tests are successful
HTTP Request: GET https://api.github.com/repos/PaloAltoNetworks/pan-os-upgrade-assurance "HTTP/1.1 200 OK"
|
Unit Tests / Verify unit tests are successful
Generating comment for PR
|
Unit Tests / Verify unit tests are successful
HTTP Request: GET https://api.github.com/repos/PaloAltoNetworks/pan-os-upgrade-assurance/contents/data.json?ref=python-coverage-comment-action-data "HTTP/1.1 404 Not Found"
|
Unit Tests / Verify unit tests are successful
HTTP Request: GET https://api.github.com/user "HTTP/1.1 403 Forbidden"
|
Unit Tests / Verify unit tests are successful
HTTP Request: GET https://api.github.com/repos/PaloAltoNetworks/pan-os-upgrade-assurance/issues/172/comments "HTTP/1.1 200 OK"
|
Unit Tests / Verify unit tests are successful
Adding new comment
|
Unit Tests / Verify unit tests are successful
HTTP Request: POST https://api.github.com/repos/PaloAltoNetworks/pan-os-upgrade-assurance/issues/172/comments "HTTP/1.1 403 Forbidden"
|
Unit Tests / Verify unit tests are successful
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).
|
Unit Tests / Verify unit tests are successful
Ending action
|
API documentation / Verify if generated API documentation is up to date
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, Gr1N/setup-poetry@v8. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Formatting and security / Verify code formatting and security
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, Gr1N/setup-poetry@v8. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Unit Tests / Verify unit tests are successful
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, Gr1N/setup-poetry@v8. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Build Docker image / Build a Docker image
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, Gr1N/setup-poetry@v8. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
documentation
|
37.2 KB |
|
pr
|
271 Bytes |
|
python-coverage-comment-action
|
472 Bytes |
|