Update Google Drive OAuth setup instructions - #6
Merged
R-YaTian merged 2 commits intoMay 20, 2026
Conversation
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Updates the Google Drive setup guide for TYSS to use OAuth Playground and a refresh token–based drive.json configuration, with added security warnings and troubleshooting notes.
Changes:
- Replaces the prior auth-code (OOB) flow with an OAuth Playground flow to obtain a refresh token.
- Updates the
drive.jsonschema to usedriveRefreshTokenand addsdriveInitOnBoot. - Adds security guidance and a small troubleshooting section for common OAuth errors.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| 3. Search for `Google Drive API` and enable it. | ||
| 4. Open `Google Auth Platform` or `OAuth consent screen`. | ||
| 5. Configure the OAuth consent screen. For personal use, fill in the required app name, user support email, and developer contact email. | ||
| 6. Add the Drive scope: |
Contributor
Author
There was a problem hiding this comment.
@copilot apply changes based on this feedback
| https://www.googleapis.com/auth/drive | ||
| ``` | ||
|
|
||
| 7. If your OAuth app remains `External` and `Testing`, Google may expire refresh tokens for the Drive scope after 7 days. To avoid that, publish the app to `In production` for personal use. |
Comment on lines
+20
to
+21
| 9. Click `+ CREATE CREDENTIALS`, then `OAuth client ID`. | ||
| 10. Set `Application type` to `Web application`. Do not use `Desktop app`. |
Comment on lines
+50
to
+53
| "driveClientID": "YOUR_WEB_CLIENT_ID_HERE", | ||
| "driveClientSecret": "YOUR_WEB_CLIENT_SECRET_HERE", | ||
| "driveRefreshToken": "YOUR_REFRESH_TOKEN_HERE", | ||
| "driveInitOnBoot": true |
Contributor
Author
|
@copilot apply changes based on the comments in this thread |
Owner
|
Have you completed all the document changes? |
Contributor
Author
|
Yes |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR updates the Google Drive setup instructions.
The existing guide uses a Desktop OAuth client and the legacy OOB copy/paste authorization code flow, then asks users to store
driveAuthCodeindrive.json. In current Google OAuth behavior, refresh tokens issued to External apps in Testing mode can expire after 7 days when using Drive scopes.This documentation update describes a tested longer-lived setup:
driveRefreshTokeninstead ofdriveAuthCodeNotes
No code changes are included. This is documentation-only.
Users are warned not to share or commit real client secrets or refresh tokens.