Skip to content

Add replace in file method, add tests #12

Add replace in file method, add tests

Add replace in file method, add tests #12

Triggered via pull request April 20, 2025 10:12
Status Success
Total duration 2m 56s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

ci.yaml

on: pull_request
call_ci  /  Prepare packaging
4s
call_ci / Prepare packaging
Matrix: call_ci / Create debian package with dh-virtualenv
Matrix: call_ci / Create debian package with FPM
call_ci  /  Create wheel package
48s
call_ci / Create wheel package
call_ci  /  Create release
0s
call_ci / Create release
Fit to window
Zoom out
Zoom in

Annotations

10 notices
call_ci / Run tests
Starting action
call_ci / Run tests
HTTP Request: GET https://api.github.com/repos/EffectiveRange/python-common-utility "HTTP/1.1 200 OK"
call_ci / Run tests
Generating comment for PR
call_ci / Run tests
HTTP Request: GET https://api.github.com/repos/EffectiveRange/python-common-utility/contents/data.json?ref=python-coverage-comment-action-data "HTTP/1.1 200 OK"
call_ci / Run tests
HTTP Request: GET https://api.github.com/user "HTTP/1.1 403 Forbidden"
call_ci / Run tests
HTTP Request: GET https://api.github.com/repos/EffectiveRange/python-common-utility/issues/14/comments "HTTP/1.1 200 OK"
call_ci / Run tests
Adding new comment
call_ci / Run tests
HTTP Request: POST https://api.github.com/repos/EffectiveRange/python-common-utility/issues/14/comments "HTTP/1.1 403 Forbidden"
call_ci / Run tests
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).
call_ci / Run tests
Ending action