bk(comment-trigger): support case insensitive#18737
Open
v1v wants to merge 2 commits intoelastic:mainfrom
Open
bk(comment-trigger): support case insensitive#18737v1v wants to merge 2 commits intoelastic:mainfrom
v1v wants to merge 2 commits intoelastic:mainfrom
Conversation
v1v
added
backport-8.19
Contributor
🤖 GitHub commentsJust comment with:
|
v1v
commented
Feb 5, 2026
| steps: | ||
| - label: "Trigger logstash-exhaustive-tests-pipeline for PRs with qa/acceptance/ changes" | ||
| if: build.pull_request.id != null && build.env("GITHUB_PR_TRIGGER_COMMENT") != "run exhaustive tests" | ||
| if: build.pull_request.id != null && build.env("GITHUB_PR_TRIGGER_COMMENT") !~ /(?i)^run\\s+exhaustive\\s+tests/ |
Member
Author
There was a problem hiding this comment.
reviewer: https://buildkite.com/docs/pipelines/configure/conditionals#variable-and-syntax-reference-operator-syntax, I assume it uses the standard regex so I can use the pattern case-insensitive
donoghuc
requested changes
Feb 6, 2026
Co-authored-by: Cas Donoghue <cas.donoghue@gmail.com>
💛 Build succeeded, but was flaky
Failed CI StepsHistory
cc @v1v |
mallendem
requested changes
Feb 10, 2026
| steps: | ||
| - label: "Trigger logstash-exhaustive-tests-pipeline for PRs with qa/acceptance/ changes" | ||
| if: build.pull_request.id != null && build.env("GITHUB_PR_TRIGGER_COMMENT") != "run exhaustive tests" | ||
| if: build.pull_request.id != null && build.env("GITHUB_PR_TRIGGER_COMMENT") !~ /(?i)^run\\s+exhaustive\\s+tests/ |
There was a problem hiding this comment.
The bot message is
🤖 GitHub comments
Just comment with:
run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)
/run exhaustive tests : Run the exhaustive tests Buildkite pipeline.
Aren't we exluding the / in /run ... by using ^?
Member
Author
There was a problem hiding this comment.
I think we can fix the comment instead
Member
Author
There was a problem hiding this comment.
Let's keep it simple here
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
5 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.
Release notes
[rn:skip]
What does this PR do?
Support GitHub comment triggers with case insensitive format.
Why is it important/What is the impact to the user?
Improve the DX
Checklist
Author's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs