Harden external-PR workflows and restrict command triggers · IntuitionMachines/python-coverage-comment-action@b175c71

Triggered via pull request March 2, 2026 03:50

e271828-

opened #3

e271828-:codex/security-gha-pr-token-exfil

Status Success

Total duration 34s

Artifacts 1

ci.yml

on: pull_request

Run tests & display coverage

30s

Annotations

10 notices

Run tests & display 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).

Run tests & display coverage

HTTP Request: POST https://api.github.com/repos/IntuitionMachines/python-coverage-comment-action/issues/3/comments "HTTP/1.1 403 Forbidden"

Run tests & display coverage

Adding new comment

Run tests & display coverage

HTTP Request: GET https://api.github.com/repos/IntuitionMachines/python-coverage-comment-action/issues/3/comments "HTTP/1.1 200 OK"

Run tests & display coverage

HTTP Request: GET https://api.github.com/user "HTTP/1.1 403 Forbidden"

Run tests & display coverage

HTTP Request: GET https://api.github.com/repos/IntuitionMachines/python-coverage-comment-action/contents/data.json?ref=python-coverage-comment-action-data "HTTP/1.1 200 OK"

Run tests & display coverage

HTTP Request: GET https://api.github.com/repos/IntuitionMachines/python-coverage-comment-action/pulls/3 "HTTP/1.1 200 OK"

Run tests & display coverage

Generating comment for PR

Run tests & display coverage

HTTP Request: GET https://api.github.com/repos/IntuitionMachines/python-coverage-comment-action "HTTP/1.1 200 OK"

Run tests & display coverage

Starting action