-
Notifications
You must be signed in to change notification settings - Fork 18
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
Documentation for Github PR Previews #12
Comments
@RinkiyaKeDad can you assist on this one? We are working on getting together a list of permissions we require from GitHub, via oauth, and why we need them. We will be including those perms in an email but we will also need them in the documentation. @maroshii can work with you on an overview of the feature and how it works, also you can use it in staging. |
We request the following permissions: PR previews added Note that upon signing up only the user permission The messages below are not meant to be what we show to the user but a guideline to why we need them. Why do we need them: RepoRepo Contents - To clone repos and deploy preview and dev environments from private repositories. OrganizationsMembers - Requested only for org installations. Not sure exactly why we need them, maybe @ifbyol can shed some light here. UserEmail - During signup. To be able to link the okteto user to the github account. |
Sure I can work on this. Could you please remind me again what the timeline for shipping this feature is? |
We hope to ship it next week. There are a few tasks we need to finish before the launch. It includes an email and the documentation listed here. We can sync next week to go over details as I need to review and create the final issues. |
As part of the preview environment github integration we need to update the docs to properly document the auto previews PR integration.
This is the page: https://www.okteto.com/docs/cloud/preview-environments/preview-environments-github/
Not sure if the idea is to deprecate the github action or not but we would need to either replace the page or create a new one.
The text was updated successfully, but these errors were encountered: