Feature summary

No response

What problem are you trying to solve?

When adding a project or GitHub repository, the current flow does not recognize repositories that are bare clones. This makes the repo appear unsupported or unavailable even though it is a valid repository state.

Proposed solution

Update the repository/project addition flow to detect bare clone repositories and treat them as valid inputs for addition. If there are any limitations, surface a clear message explaining the constraint instead of failing silently or rejecting the repo outright.

Workflow impact

This would remove a setup blocker for users working with bare clones and make repository onboarding more reliable, especially in environments where repositories are mirrored or managed in bare form.

Installation context

GitHub App repository addition flow

Additional context

If relevant, the repository may be managed as a bare clone rather than a working tree checkout.