Extension point for exposing default branches #15
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
|
Need at least one (preferably multiple) reference implementations, and at least one reference caller, as downstream PRs demonstrating end-to-end usage. |
|
agree... @jglick the main use for this is GUI related, are you aware of other needs for this? |
|
🐛 I would prefer if the default branch was handled via the new Categorization API |
|
yes agree, closing this for that reason |
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.
Ticket: JENKINS-38718
I believe this probably belongs in scm-api, as it is the common denominator that various systems share (github will have to implement this, but not git, as I don't think git has the concept of a default branch, but github does, for example).
Just opening for discussion...