Cleaner exit when user credentials are incorrect #2753
JimMadgetest_code.yaml
on: pull_request
test_python
6m 31s
test_markdown_links
8s
Annotations
10 notices
|
test_python
Starting action
|
|
test_python
HTTP Request: GET https://api.github.com/repos/alan-turing-institute/data-safe-haven "HTTP/1.1 200 OK"
|
|
test_python
Generating comment for PR
|
|
test_python
HTTP Request: GET https://api.github.com/repos/alan-turing-institute/data-safe-haven/contents/data.json?ref=python-coverage-comment-action-data "HTTP/1.1 200 OK"
|
|
test_python
HTTP Request: GET https://api.github.com/user "HTTP/1.1 403 Forbidden"
|
|
test_python
HTTP Request: GET https://api.github.com/repos/alan-turing-institute/data-safe-haven/issues/2296/comments "HTTP/1.1 200 OK"
|
|
test_python
Update previous comment
|
|
test_python
HTTP Request: PATCH https://api.github.com/repos/alan-turing-institute/data-safe-haven/issues/comments/2479337074 "HTTP/1.1 403 Forbidden"
|
|
test_python
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).
|
|
test_python
Ending action
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
python-coverage-comment-action
|
1.62 KB |
|