Some branches may be missing from the build target drop-down list due to a display limit of 100 branches (30 for Unity Version Control). Branches without recent commits might not appear because the list prioritizes branches with recent activity. To resolve this, make a small commit and push it to the missing branches to update their status and improve visibility.
Symptoms:
- Some branches are missing from the drop-down list used to select the branches to be built.
- The branches were available some days ago but are now missing from the Build target configuration.
- The branches are visible in my version control system but not in UBA.
Cause:
The branch selection drop-down list has a limit of displaying only 100 branches. However, for Unity Version Control (UVCS), the limit is 30 branches.
The order of displayed branches depends on the version control system:
- For UVCS, branches with the oldest commits appear first.
- For other source control providers (e.g., GitLab, GitHub, Bitbucket), branches are returned in the order listed by Git, which is determined by the remote server.
Branches without recent commits may be missing due to the branch display limit.
Resolution:
Make a small commit and push it to the missing branches:
- Perform a minor update (e.g., add a comment or whitespace change).
- Push the update to the missing branches.
- This ensures that recent updates are recognized and may make the branch appear in the selection list.
If you have more than 100 branches (or 30 for UVCS), be aware that the drop-down list will not display all branches.
Ensure that important branches have recent commits to improve their visibility in the drop-down list.
More information: