@angus and I just spent quite some time on figuring out why a theme did not update when it was updated in Github. We finally found that the theme was being pulled from d-compat/2026.5 instead of main.
Turns out that the branch popup says “branch: main” but if you leave it empty, it will set branch to nil and not main because main is an input placeholder and not a prefilled value.
I’d almost call this a bug and not just a UX issue (also, I’ve little idea how to fix) so alerting an engineer, maybe @martin you have experience with the admin side? Can you take a look or triage?
Not so sure… I think this would be sufficiently resolved if the placeholder was “Choose a specific branch or keep empty”
Wouldn’t that lead to the same problem? You’d keep the input empty (trusting the placeholder) and then it defaults back to nil?
I would think that the ideal state is that it does default to main?
No.
Leaving it empty will automatically select the correct d-compat branch.
Setting it to main will override that and will force-use the main branch.
The problem is that the placeholder currently implies that leaving it empty will select main.
If the copy is changed to something that does not imply that, the confusion will be gone.
Ah ok, thanks for the clarification – not my forté this area.
Seems like you’re right then, easy change to make.
