ci: fixes target branch definition to support multiple releases automatically #2532
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
…atically Signed-off-by: Vincent Biret <vibiret@microsoft.com>
adrian05-ms
approved these changes
Oct 6, 2025
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
The auto-release detection on support/v1 has not been working as expected forcing me to create those releases manually.
https://github.com/microsoft/OpenAPI.NET/actions/runs/18290786080/job/52077236107
This is time consuming, and not my primary responsibility.
This PR aims to dynamically set the target branch based off the trigger to patch for the failing automatic branch detection