You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 23, 2023. It is now read-only.
While syncing with GitHub, it simply asks for all my private and public repositories.
Here is a screenshot of how it looks:
Though it might not be misused by the app, it would always be a great idea to have a custom message displayed at the app side before even going forward with syncing.
In this way, user knows what Press is going to do with all the repositories and why it is asking.
The text was updated successfully, but these errors were encountered:
Agree that that is quite scary. I'll add a rationale dialog to try explaining the permission before opening the auth page.
Assuming your target user base are tech friendly, how about just having a simple EditText in the app asking for the repository URL and only sync that?
The URL isn't sufficient, a private SSH key is required as well for granting Press access to your repository. Expecting users to generate an SSH key-pair on their computer and paste their private key in the app is a huge entry barrier. I could consider offering it as an option for paranoid users in the future, but I don't know if it's worth putting in effort right now.
saket
changed the title
Scary Permissions being asked for GitHub sync
Scary permissions being asked for GitHub sync
Jan 18, 2021
I should also add that this is the smallest set of permissions a GitHub app can request for adding a deploy key to a single git repository. I wish there was a narrower permission.
While syncing with GitHub, it simply asks for all my private and public repositories.
Here is a screenshot of how it looks:
Though it might not be misused by the app, it would always be a great idea to have a custom message displayed at the app side before even going forward with syncing.
In this way, user knows what Press is going to do with all the repositories and why it is asking.
The text was updated successfully, but these errors were encountered: