Handle project access for non-repository members
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Problem to solve
Users that don't have access to a repository they run into errors and empty pages when access a project in Gitpod.
Steps to reproduce
- Create a private repository in any of the available providers
- Add a new project in a new team in Gitpod
- Invite a team member in the new team who does have access to the repository in the corresponding provider
- Log in with the invited team member and try accessing the project branches or opening a workspace
| Empty branches page | Error when opening a workspace |
|---|---|
 |
 |
Proposal
TBD (To be discussed)
This can become more relevant as users adopt Teams & Projects and create teams with multiple projects across different providers with team members that don't necessarily have access to corresponding repositories. 💡
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
Start by reproducing the issue with the listed private-repository and team-member steps, checking both the project branches page and workspace opening flow. Define the expected behavior for a team member without repository access and verify that access is handled with a clear result instead of an empty page or error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authorization
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100