Current Behavior

• UI calls backend to validate repository / resolve default branch
• Backend delegates to Sztabina (/repos/default-branch-by-url)
• Sztabina returns specific failure reasons (e.g. “only HTTPS URLs are supported”)
• Backend collapses this into a generic error
• UI displays a generic, sometimes incorrect message

Example:

• Input: http://tigase.dev/sztab
• Actual failure: Sztabina rejects non-HTTPS URLs
• UI message: “Invalid Git repository or credentials: Failed to resolve default branch”

Expected Behavior

• Backend should preserve and propagate Sztabina error messages (or structured error codes)
• UI should display the specific error returned by Sztabina
• Users should see actionable feedback (e.g. “Only HTTPS Git URLs are supported”)

Impact

• Confusing and misleading UX during project creation
• Users may assume credential or repository issues when the problem is URL scheme
• Increases trial-and-error and support burden

Reproduction Steps

1. Open “Create Project” dialog
2. Enter a Git repository URL using http:// (not https://)
3. Provide valid username and PAT
4. Click “Validate repository”

Actual Result

Generic error message shown:

Invalid Git repository or credentials: Failed to resolve default branch

Expected Result

Specific error message shown:

Only HTTPS Git URLs are supported

Priority

Low–Medium (post-release polish)