-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable collaborators #20353
base: main
Are you sure you want to change the base?
Enable collaborators #20353
Changes from all commits
6c5616c
52ac1e7
63b5901
69f080e
69bdeaa
92193b3
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -158,7 +158,9 @@ export class ContextService { | |
user.id, | ||
context.repository.cloneUrl, | ||
options?.organizationId, | ||
true, | ||
); | ||
// todo(ft): solve for this case with collaborators who can't select projects directly | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'd love ideas around this: how can we not block collaborators if a repo they're working on gets imported twice? Or, in the very least, how do we educate members and owners about this possibility? It's admittedly a case on the edge™, but IMO worth considering. |
||
if (projects.length > 1) { | ||
throw new ApplicationError(ErrorCodes.BAD_REQUEST, "Multiple projects found for clone URL."); | ||
} | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -92,7 +92,7 @@ schema: |- | |
permission read_billing = member + owner + installation->admin | ||
permission write_billing = owner + installation->admin | ||
|
||
permission read_prebuild = member + owner + installation->admin | ||
permission read_prebuild = collaborator + member + owner + installation->admin | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This org-wide read prebuild permission I flipped on accidentally when looking for the project-specific one, and it ended up raising a question: do we want to let collaborators view the list of prebuilds of the org? I'm guessing not, because we'd have to change those the related pages quite a bit (to signal that you can't start / stop prebuilds or view any of their settings), but it very theoretically could be useful if they wanted to at check what's wrong with a repo's prebuild config and if it's something they can fix themselves. |
||
|
||
permission create_workspace = member + collaborator | ||
|
||
|
@@ -118,10 +118,10 @@ schema: |- | |
permission write_info = editor + org->owner + org->installation_admin | ||
permission delete = editor + org->owner + org->installation_admin | ||
|
||
permission read_env_var = viewer + editor + org->owner + org->installation_admin | ||
permission read_env_var = viewer + editor + org->collaborator + org->owner + org->installation_admin | ||
permission write_env_var = editor + org->owner + org->installation_admin | ||
|
||
permission read_prebuild = viewer + editor + org->owner + org->installation_admin | ||
permission read_prebuild = viewer + editor + org->collaborator + org->owner + org->installation_admin | ||
permission write_prebuild = editor + org->owner | ||
} | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These super rad debug logs I accidentally left in with #20287. Yikes!