SC action: add input to select SC branch #6
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
tremblap
reviewed
Jun 9, 2025
Member
tremblap
left a comment
tremblap
left a comment
There was a problem hiding this comment.
would that mean we can trigger 2 set of binaries?
| default: 'main' | ||
| sc_branch: | ||
| description: 'Select an SC branch to use' | ||
| requireed: false |
jamesb93
approved these changes
Jun 10, 2025
| default: 'main' | ||
| sc_branch: | ||
| description: 'Select an SC branch to use' | ||
| requireed: false |
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.
Because of changes to SC in relation to our code crimes, we will need to be selective about which SC branch(es) we're releasing against, rather than just tugging on
main. Furthermore, we might want to support dual releases during 3.13 to 3.14 transition (and again for 3.15).