Repository navigation
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
🔎 Supported by static analysis
🌐 Web query:
GitHub official documentation pull_request_target default policy evaluate mode November 2 2026 affected public repositories general availability💡 Result:
🏁 Script executed:
Repository: substrait-io/substrait-java
Length of output: 4951
🏁 Script executed:
Repository: substrait-io/substrait-java
Length of output: 1400
Clarify when the default policy takes effect.
GitHub’s default
pull_request_targetpolicy is currently in evaluate mode. GitHub plans to enforce it on November 2, 2026 for affected public repositories that used the default policy before general availability. The current wording implies an immediate block and does not state the affected scope.Suggested wording
📝 Committable suggestion
🤖 Prompt for AI Agents