New project form missing empty-state message when there are no repositories
Open
Nobody has claimed this yet.
component: dashboard
meta: never-stale
team: webapp
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
The new project form is confusing when there are no repositories under the current git-provider / org.
Suggested fix
An empty state message should say something like
No repositories found - select a different org or Git provider above.
To reproduce (from internal)
- I used the integration panel to setup an integration with Gitlab
- Once authorized, I navigated to proejcts
- Clicked new Project
- At the time of linking, I did not have any repository on gitlab. Have not tested what happens if I have them, but not grant access to gitpod.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the flow by authorizing a GitLab integration, opening Projects, and selecting New Project with no repositories available. Locate the new project form, then verify that an empty-state message guides users to select a different organization or Git provider when no repositories are found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100