Repository navigation
Fix settings for default-branch repositories - #8
Merged
Merged
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
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.
Seeded repositories can have a null branch list while tracking the default branch. Opening their Settings tab called
.slice()on null and left the previous panel displayed. Treat a missing branch list as empty while preserving default-branch tracking, so the settings form and Git timeout selector render correctly.Validation: regression coverage renders the actual settings template for null, missing, empty and explicit branch lists, verifies inherited timeout selection and checks that edits do not mutate the stored list. Website checks, production web build and public-artifact audit pass.