[Feat] - Hide branches management UI

[Barruchou]

Following this discussion on Discord:

https://discord.com/channels/1139017922073866332/1139017922895937598/1170003038942003210

Here is a PR to allow you to hide branch management elements from the interface.

[changeset-bot]

⚠️ No Changeset found

Latest commit: a954bd5

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
keystatic-site	✅ Ready (Inspect)	Visit Preview	Nov 14, 2023 2:16pm

3 Ignored Deployments

Name	Status	Preview	Updated (UTC)
keystar-ui	⬜️ Ignored (Inspect)	Visit Preview	Nov 14, 2023 2:16pm
keystatic	⬜️ Ignored (Inspect)	Visit Preview	Nov 14, 2023 2:16pm
keystatic-next-blocks-builder	⬜️ Ignored (Inspect)	Visit Preview	Nov 14, 2023 2:16pm

[jossmac]

This will break core functionality. For example, if there's branch protection on main and a user is prompted to create a new branch they'll be stranded with no way to navigate.

[Barruchou]

Hello @jossmac

There is no config to change the default branch (other than "main")? In this case it would leave the developer the choice to have a "content" branch (for example) and continue to protect his "main" branch. Or allow you to define a fallback branch which would be used in the case of a protected "main".

What do you think ?

[jossmac]

Hi @Barruchou, sorry I meant "default branch" but said main so it aligned with the screenshot. We'll look into an approach that allows consumers to configure a "content branch" or similar, but simply hiding UI that breaks functionality isn't a viable solution.

[jossmac]

This is something we'd like to explore, if there's community interest. @Barruchou could you create a discussion?

[Barruchou]

And here it is: #759