dotya.ml/ community

Team member can't access team repository #44

New Issue

Closed

opened 2021-08-13 21:00:38 +02:00 by kreyren · 8 comments

kreyren commented

2021-08-13 21:00:38 +02:00

![image](/attachments/07049623-c336-4e02-8419-0074e012bad6) ![image](/attachments/5d538398-8eca-43a2-9379-7d79d7906cb6)

57 KiB

50 KiB

kreyren commented

2021-08-13 21:01:30 +02:00

Author

💢

![image](/attachments/9c39ec7f-4e0c-4a29-a9c1-04b668122d9a) 💢

17 KiB

renameMeOnMP4.zip

3.2 MiB

kreyren commented

2021-08-13 21:02:03 +02:00

Author

CC @molese

CC @wanderer CC @molese

wanderer commented

2021-08-13 21:22:07 +02:00

Owner

I hate to ask but have you tried a hard reload? @kreyren

I hate to ask but have you tried a hard reload? @kreyren

wanderer commented

2021-08-13 21:22:50 +02:00

Owner

by the looks of it, access permissions are set correctly..

by the looks of it, access permissions are set correctly..

kreyren commented

2021-08-13 23:02:00 +02:00

Author

I hate to ask but have you tried a hard reload? @kreyren

elaborate hard reload

> I hate to ask but have you tried a hard reload? @kreyren elaborate hard reload

kreyren commented

2021-08-14 10:55:29 +02:00

Author

Solved: I had to enable the pull requests in team perms

Solved: I had to enable the pull requests in team perms ![image](/attachments/60968148-c00c-48ea-bf4d-a0a8f72f3a07)

34 KiB

kreyren closed this issue

2021-08-14 10:55:29 +02:00

wanderer commented

2021-08-14 12:48:24 +02:00

Owner

Hm that is weird. Shouldn't repo read access be enough to, well, read the repo contents?

I feel like permission to create PRs and repo access should not depend on each other this way.

To create a PR, sure, you do need a read access to the repo first.
To read a repo, though, you shouldn't need a PR access, IMO...

I think it might be an problem with the implementation.
If you feel like it, you could open an issue upstream and link this.

Hm that is weird. Shouldn't repo read access be enough to, well, read the repo contents? I feel like permission to create PRs and repo access should not depend on each other this way. To create a PR, sure, you do need a read access to the repo first. To read a repo, though, you shouldn't need a PR access, IMO... I think it might be an problem with the implementation. If you feel like it, you could open an issue upstream and link this.

kreyren commented

2021-08-14 20:32:06 +02:00

Author

Hm that is weird. Shouldn't repo read access be enough to, well, read the repo contents?

Ye weird that he coudn't access the code, but FWIW i like that it's separete to allow access in pull requests

If you feel like it, you could open an issue upstream and link this.

Too much effort I rather focus my work on my solution

> Hm that is weird. Shouldn't repo read access be enough to, well, read the repo contents? Ye weird that he coudn't access the code, but FWIW i like that it's separete to allow access in pull requests > If you feel like it, you could open an issue upstream and link this. Too much effort I rather focus my work on my solution

Sign in to join this conversation.

No Label

upstream-related

No Milestone

No project

No Assignees

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: dotya.ml/community#44

No description provided.