|
|
|
|
|
by ickyforce
1682 days ago
|
|
I don't like the fact that I need to grant read/write access to all public and private repositories to use the dashboard or create PRs. I know that github has no decent solution to limit access scope to 1 repository but this is the reason why I haven't tested graphite on any real work.
I guess that the only sane way would be to create a separate github user which only has access to a single repo where I'd like to use/test graphite. At the same time I'd probably be ok with the CLI having wider access, as long as the website does not have it. I can control/monitor CLI to some degree but not the web part. |
|