Don't trigger CI when pushing branches #240
Merged
Conversation
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
This commit stops triggering BK from triggering CI when branches get pushed. We rely on CI for PRs, instead, which is handled by the BK PR Bot.
alexsapran
approved these changes
Jan 13, 2025
💚 Build Succeeded
cc @dliappis |
|
@logstashmachine backport 8.x |
github-actions bot
pushed a commit
that referenced
this pull request
Jan 13, 2025
This commit stops triggering BK from triggering CI when branches get pushed. We rely on CI for PRs, instead, which is handled by the BK PR Bot. (cherry picked from commit 63aa130)
|
The backport raised in #240 (comment) was just to test CI via backport automation (all good -> https://buildkite.com/elastic/logstash-filter-elastic-integration-pull-request/builds/488) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
This commit stops triggering BK from triggering CI when branches get pushed. We rely on CI for PRs, instead, which is handled by the BK PR Bot.