[renovate] Match all branches instead of backporting for FTR group #205285
Conversation
This file contains 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
FTR needs to be kept up to date across all branches, but using the backport automation ends up requiring manual intervention due to merge conflicts. This configures renovate to open separate pull requests per branch. If this works as expected I'll do another pass and see if there's other groups that this makes sense for.
jbudz
added
Team:Operations
|
Pinging @elastic/kibana-operations (Team:Operations) |
💚 Build Succeeded
|
Ikuni17
approved these changes
Dec 30, 2024
stratoula
pushed a commit
to stratoula/kibana
that referenced
this pull request
Jan 2, 2025
…lastic#205285) FTR dependencies needs to be kept up to date across all branches, but using the backport automation ends up requiring manual intervention due to merge conflicts. This configures renovate to open separate pull requests per branch for the `ftr` group. If this works as expected I'll do another pass and see if there's other groups that this makes sense for.
benakansara
pushed a commit
to benakansara/kibana
that referenced
this pull request
Jan 2, 2025
…lastic#205285) FTR dependencies needs to be kept up to date across all branches, but using the backport automation ends up requiring manual intervention due to merge conflicts. This configures renovate to open separate pull requests per branch for the `ftr` group. If this works as expected I'll do another pass and see if there's other groups that this makes sense for.
cqliu1
pushed a commit
to cqliu1/kibana
that referenced
this pull request
Jan 2, 2025
…lastic#205285) FTR dependencies needs to be kept up to date across all branches, but using the backport automation ends up requiring manual intervention due to merge conflicts. This configures renovate to open separate pull requests per branch for the `ftr` group. If this works as expected I'll do another pass and see if there's other groups that this makes sense for.
jbudz
added a commit
that referenced
this pull request
Jan 3, 2025
Follow up to #205285 This uses renovate instead of backport tooling on a few more of operation's groups. These were selected because they have not required any code changes to date.
kowalczyk-krzysztof
pushed a commit
to kowalczyk-krzysztof/kibana
that referenced
this pull request
Jan 7, 2025
Follow up to elastic#205285 This uses renovate instead of backport tooling on a few more of operation's groups. These were selected because they have not required any code changes to date.
CAWilson94
pushed a commit
to CAWilson94/kibana
that referenced
this pull request
Jan 13, 2025
…lastic#205285) FTR dependencies needs to be kept up to date across all branches, but using the backport automation ends up requiring manual intervention due to merge conflicts. This configures renovate to open separate pull requests per branch for the `ftr` group. If this works as expected I'll do another pass and see if there's other groups that this makes sense for.
CAWilson94
pushed a commit
to CAWilson94/kibana
that referenced
this pull request
Jan 13, 2025
Follow up to elastic#205285 This uses renovate instead of backport tooling on a few more of operation's groups. These were selected because they have not required any code changes to date.
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.
FTR dependencies needs to be kept up to date across all branches, but using the backport automation ends up requiring manual intervention due to merge conflicts.
This configures renovate to open separate pull requests per branch for the
ftrgroup. If this works as expected I'll do another pass and see if there's other groups that this makes sense for.