ci(formal): skip informational PR comment on forked PRs#17497
Closed
napetrov wants to merge 3 commits intoopenclaw:mainfrom
Closed
ci(formal): skip informational PR comment on forked PRs#17497napetrov wants to merge 3 commits intoopenclaw:mainfrom
napetrov wants to merge 3 commits intoopenclaw:mainfrom
Conversation
4 tasks
…lve formal-conformance workflow conflict
…t spy type inference
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Comment on PR (informational)step in.github/workflows/formal-conformance.ymlgithub.event.pull_request.head.repo.full_name == github.repositoryWhy
Fork PRs often have restricted token permissions, so posting PR comments from workflow can fail with:
Resource not accessible by integration(HTTP 403)This currently marks
formal_conformanceas failed even though the check is informational.Effect
Related context: #16761
Greptile Summary
Adds a fork-guard to the "Comment on PR (informational)" step in the formal conformance workflow. The step now only posts a PR comment when the PR originates from the same repository, preventing 403 errors (
Resource not accessible by integration) on fork PRs where theGITHUB_TOKENlackspull-requests: writescope.&& github.event.pull_request.head.repo.full_name == github.repositoryto the existingifcondition on line 110Confidence Score: 5/5
Last reviewed commit: 8eb4c7b
(4/5) You can add custom instructions or style guidelines for the agent here!
AI Assistance & Contributing Transparency