Conversation
Related to #21295 (comment)
github-actions
bot
added
the
development-process
alamb
approved these changes
Apr 3, 2026
| - "**.md" | ||
| - ".github/ISSUE_TEMPLATE/**" | ||
| - ".github/pull_request_template.md" | ||
| merge_group: |
Contributor
There was a problem hiding this comment.
It seems like this change means the merge queue will not try and stage all commits ahead of this one in the queue -- I think that is ok for now. We can add it back later when needed
Contributor
|
Let's give it a try (test in production 🥳 🦜 ) |
Contributor
|
We seem to be back to green after this PR: 
Thank you @blaginin |
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
2 participants
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.
Related to fix(unparser): use to_rfc3339 for default TIMESTAMPTZ formatting #21295 (comment)
Follow on to Merge queue: make dev checks required + add .asf.yaml validation #21239
Which issue does this PR close?
Rationale for this change
What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?