Adjusting inbetween release process to use dev branches #2956
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
artem-shelkovnikov
approved these changes
Nov 13, 2024
seanstory
added a commit
that referenced
this pull request
Nov 13, 2024
#2961) Co-authored-by: Sean Story <[email protected]>
seanstory
added a commit
that referenced
this pull request
Nov 13, 2024
…#2960) Co-authored-by: Sean Story <[email protected]>
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.
Related to https://elasticco.atlassian.net/browse/ENGPRD-829
Our "in between" release process has been broken since Elastic made org-wide changes to our github rulesets, requiring PRs for commits made to maintenance branches.
This therefore adjusts the formal description of the process to explain how a dev branch can be used. It also removes the branch gating for the buildkite build.
Pre-Review Checklist
v7.13.2,v7.14.0,v8.0.0)