Skip to content

Conversation

karenzone
Copy link
Contributor

@karenzone karenzone commented Oct 3, 2025

@karenzone karenzone requested a review from robbavey October 3, 2025 22:31
@karenzone karenzone self-assigned this Oct 3, 2025
@karenzone karenzone added the docs label Oct 3, 2025
Copy link
Contributor

github-actions bot commented Oct 3, 2025

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

Copy link
Contributor

github-actions bot commented Oct 3, 2025

🔍 Preview links for changed docs

@karenzone karenzone added the backport-active-9 Automated backport with mergify to all the active 9.[0-9]+ branches label Oct 3, 2025
@elastic elastic deleted a comment from mergify bot Oct 3, 2025
Copy link
Member

@robbavey robbavey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@karenzone karenzone merged commit 8f4014b into elastic:main Oct 7, 2025
14 checks passed
@karenzone karenzone deleted the 14422-test-boolean branch October 7, 2025 22:41
Copy link
Contributor

github-actions bot commented Oct 7, 2025

@Mergifyio backport 9.0 9.1 9.2

Copy link
Contributor

mergify bot commented Oct 7, 2025

backport 9.0 9.1 9.2

✅ Backports have been created

mergify bot pushed a commit that referenced this pull request Oct 7, 2025
mergify bot pushed a commit that referenced this pull request Oct 7, 2025
mergify bot pushed a commit that referenced this pull request Oct 7, 2025
karenzone added a commit that referenced this pull request Oct 7, 2025
karenzone added a commit that referenced this pull request Oct 7, 2025
karenzone added a commit that referenced this pull request Oct 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-active-9 Automated backport with mergify to all the active 9.[0-9]+ branches docs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

"Best practice" for testing whether boolean field exists is broken

2 participants