Is your feature request related to a problem?
Not a problem necessarily, but I did run into some problems getting the repo configuration setup initially. I think this could help folks that are onboarding by providing faster feedback cycles and fewer context switches

Which solution do you suggest?

• When a user blurs the git repo input, access to the repo is validated and the result is shown to the user. To minimize UX impact, it can be informational more than anything, but any indication would be great.
• In the advanced settings, a searchable dropdown is implemented for the branch input. A user can type and filter branches so they don't have to swap windows to copy/paste

This small change could reduce setup friction for new users and make DevPod feel more responsive to common misconfigurations.

Which alternative solutions exist?
I don't think alternative is the right word here. It works fine currently, this just exposes issues earlier in the workflow so users don't have to re-enter the other fields after each failure

Additional context
Creating per the contributing docs. I'd love to open a PR for this, but don't want to embark on it if maintainers don't want this feature