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.
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
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
💢
CC @wanderer
CC @molese
I hate to ask but have you tried a hard reload? @kreyren
by the looks of it, access permissions are set correctly..
elaborate hard reload
Solved: I had to enable the pull requests in team perms
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.
Ye weird that he coudn't access the code, but FWIW i like that it's separete to allow access in pull requests
Too much effort I rather focus my work on my solution