Skip to content

docs: update Google OAuth review guide with YC office hour insights#6165

Merged
sapnesh-nango merged 3 commits into
masterfrom
sapnesh/nan-5582-update-google-oauth-approval-guide-with-insights-from
May 24, 2026
Merged

docs: update Google OAuth review guide with YC office hour insights#6165
sapnesh-nango merged 3 commits into
masterfrom
sapnesh/nan-5582-update-google-oauth-approval-guide-with-insights-from

Conversation

@sapnesh-nango

@sapnesh-nango sapnesh-nango commented May 17, 2026

Copy link
Copy Markdown
Contributor

Preview link: https://nango-sapnesh-nan-5582-update-google-oauth-approval-guide-w.mintlify.app/

Summary

  • Expanded the Google App & Security Review guide with insights from the May 2026 Google × YC OAuth Approval office hour: contact-email pitfalls, hidden Submit button, scope-match-everywhere, demo video specifics, AI/data-use rules, branding/TM requirements, the three homepage definitions, privacy-policy patterns (OpenText/Zoho), two-team review structure, granular consent handling, and renewal extensions.
  • Added Google's reference timelines (brand 2-3 days, sensitive ~10 days, restricted 6 weeks officially / ~10 weeks average) alongside the existing Nango ranges so readers can calibrate expectations.
  • Fixed 5 broken Google doc URLs (Limited Use, AI/ML use cases, Partner Marketing Hub, Partner Advantage) by pointing to current canonical pages.

Test plan

  • mintlify broken-links passes from docs/
  • All external URLs in the file return 200 (verified via curl loop)
  • Local mintlify dev preview renders the new sub-sections correctly

Resolves NAN-5582

@linear

linear Bot commented May 17, 2026

Copy link
Copy Markdown

NAN-5582

@mintlify

mintlify Bot commented May 17, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
nango 🟢 Ready View Preview May 17, 2026, 4:18 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@superagent-security superagent-security Bot added the contributor:verified Contributor passed trust analysis. label May 17, 2026

@nango-repository-pusher nango-repository-pusher Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Auto-approved: docs-only change.

@sapnesh-nango sapnesh-nango requested a review from rguldener May 17, 2026 16:17

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 issue found across 1 file

Confidence score: 5/5

  • This PR appears low risk and safe to merge: the only reported issue is a documentation typo in docs/api-integrations/google-shared/google-security-review.mdx with very low severity (1/10).
  • The issue is wording-only (“Not that” vs “Note that”) and does not indicate functional, runtime, or regression impact.
  • Pay close attention to docs/api-integrations/google-shared/google-security-review.mdx - correct the typo so the sentence clearly warns that the email goes to the contact address.
Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="docs/api-integrations/google-shared/google-security-review.mdx">

<violation number="1" location="docs/api-integrations/google-shared/google-security-review.mdx:363">
P3: Typo: 'Not that' should be 'Note that'. The sentence intends to tell the reader to be aware that the email goes to the contact address, not to negate something.</violation>
</file>

Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
Fix all with cubic | Re-trigger cubic

Comment thread docs/api-integrations/google-shared/google-security-review.mdx Outdated

@nango-repository-pusher nango-repository-pusher Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Auto-approved: docs-only change.

@rguldener rguldener left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left some comments for smaller changes, then good to go!

Overall we should show that with this guide & proper prep, passing the review process is not a big deal and something that can be done in a reasonable amount of time, even as an early stage startup.

Comment thread docs/api-integrations/google-shared/google-security-review.mdx Outdated
Comment thread docs/api-integrations/google-shared/google-security-review.mdx
Comment thread docs/api-integrations/google-shared/google-security-review.mdx Outdated
Comment thread docs/api-integrations/google-shared/google-security-review.mdx Outdated
Comment thread docs/api-integrations/google-shared/google-security-review.mdx Outdated
Comment thread docs/api-integrations/google-shared/google-security-review.mdx
@gitguardian

gitguardian Bot commented May 24, 2026

Copy link
Copy Markdown

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
While these secrets were previously flagged, we no longer have a reference to the
specific commits where they were detected. Once a secret has been leaked into a git
repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

@sapnesh-nango sapnesh-nango force-pushed the sapnesh/nan-5582-update-google-oauth-approval-guide-with-insights-from branch from 876b4e4 to d4c59f4 Compare May 24, 2026 13:47
@superagent-security superagent-security Bot added the pr:verified PR passed security analysis. label May 24, 2026

@nango-repository-pusher nango-repository-pusher Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Auto-approved: docs-only change.

@superagent-security superagent-security Bot added pr:flagged PR flagged for review by security analysis. and removed pr:verified PR passed security analysis. labels May 24, 2026
@superagent-security superagent-security Bot added pr:verified PR passed security analysis. and removed pr:flagged PR flagged for review by security analysis. labels May 24, 2026

@nango-repository-pusher nango-repository-pusher Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Auto-approved: docs-only change.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 46fc26811d

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread docs/api-integrations/google-shared/google-security-review.mdx
@sapnesh-nango sapnesh-nango added this pull request to the merge queue May 24, 2026
Merged via the queue into master with commit aebddf7 May 24, 2026
29 checks passed
@sapnesh-nango sapnesh-nango deleted the sapnesh/nan-5582-update-google-oauth-approval-guide-with-insights-from branch May 24, 2026 14:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

contributor:verified Contributor passed trust analysis. pr:verified PR passed security analysis.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants