# Misleading "branch" input in theme import

**URL:** https://meta.discourse.org/t/misleading-branch-input-in-theme-import/404507
**Category:** UX
**Tags:** fixed
**Created:** [June 4, 2026, 9:23am UTC](https://meta.discourse.org/t/misleading-branch-input-in-theme-import/404507 "2026-06-04T09:23:24Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [June 4, 2026, 11:40am UTC](https://meta.discourse.org/t/misleading-branch-input-in-theme-import/404507/5 "2026-06-04T11:40:36Z")

</div>

> [@chapoi](#):
>
> 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.

> [@chapoi](#):
>
> You’d keep the input empty (trusting the placeholder)

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.

---

_[View the full topic](https://meta.discourse.org/t/misleading-branch-input-in-theme-import/404507)._