When the safe output create-pull-request is configured to fallback-to-issue (in protected-files attribute) and the changes involve protected files, the pull request isn't actually created but the job summary states the pull request has been actually created.
It should state issue was created as a fallback (instead of claiming the PR has been created) (preferably with a link to the created issue)
If the agent is acting on a PR and the agent is instructed to add-comment the comment body also claims the PR was created.
The comment should be consistent as well, stating the PR wasn't created but a fallback issue has been created (preferably with a link to the created issue)
If the create-pull-request is configured to block PR creation, then that should also be consistent and logged accordingly.
When the safe output
create-pull-requestis configured tofallback-to-issue(inprotected-filesattribute) and the changes involve protected files, the pull request isn't actually created but the job summary states the pull request has been actually created.It should state issue was created as a fallback (instead of claiming the PR has been created) (preferably with a link to the created issue)
If the agent is acting on a PR and the agent is instructed to
add-commentthe comment body also claims the PR was created.The comment should be consistent as well, stating the PR wasn't created but a fallback issue has been created (preferably with a link to the created issue)
If the
create-pull-requestis configured to block PR creation, then that should also be consistent and logged accordingly.