GH-50553: [Dev] Clarify invalid PR title guidance comment#50554
Merged
Conversation
Reranko05
requested review from
assignUser,
jonkeane,
kou and
raulcd
as code owners
July 20, 2026 13:01
|
|
|
After merging your PR, Conbench analyzed the 4 benchmarking runs that have been run so far on merge-commit 6b3a94c. There were 3 benchmark results indicating a performance regression:
The full Conbench report has more details. It also includes information about 306 possible false positives for unstable benchmarks that are known to sometimes produce them. |
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.
Rationale for this change
The developer PR workflow automatically converts pull requests with invalid titles to drafts and posts a guidance comment. The current comment explains the required title format, but it doesn't explicitly state why the pull request was converted to a draft or that contributors should mark it as ready for review after fixing the title.
This change makes those steps clearer to contributors.
What changes are included in this PR?