chore(source-gong): update external documentation URLs in metadata

[devin-ai-integration]

What

source-gong's externalDocumentationUrls pointed at https://us-66463.app.gong.io/..., a tenant-specific Gong subdomain that requires a login to that particular instance, so automated deprecation monitoring can't read it. Gong publishes the same content publicly on help.gong.io. This also adds the two doc types that were missing (api_release_history, api_deprecations), which are what the API deprecation monitoring playbook checks first.

Found while running the API Deprecation Monitoring playbook for the Gong API family.

Resolves https://github.com/airbytehq/oncall/issues/10402

• https://github.com/airbytehq/oncall/issues/10402

Requested by: Danylo Jablonski.

How

Metadata-only edit to airbyte-integrations/connectors/source-gong/metadata.yaml:

• api_reference, rate_limits → https://help.gong.io/apidocs (public V2 API reference; the rate-limit section lives on that page)
• authentication_guide → https://help.gong.io/docs/create-an-app-for-gong (OAuth app creation + token flow)
• added api_release_history → https://help.gong.io/docs/release-notes
• added api_deprecations → https://help.gong.io/docs/public-api-change-deprecating-call-action-items-in-the-extensive-endpoint

All five URLs verified to return 200 with public content. No version bump — docs-URL-only metadata changes don't affect connector behavior (precedent: b02a7b2, source-github).

Review guide

1. airbyte-integrations/connectors/source-gong/metadata.yaml

User Impact

None at runtime. Improves the accuracy of connector metadata and of future upstream-deprecation checks.

Can this PR be safely reverted and rolled back?

• YES 💚
• NO ❌

Link to Devin session: https://app.devin.ai/sessions/eadf5575c65044bc8fd01634b060040a

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring

[octavia-bot]

Note

📝 PR Converted to Draft

More info...

Thank you for creating this PR. As a policy to protect our engineers' time, Airbyte requires all PRs to be created first in draft status. Your PR has been automatically converted to draft status in respect for this policy.

As soon as your PR is ready for formal review, you can proceed to convert the PR to "ready for review" status by clicking the "Ready for review" button at the bottom of the PR page.

To skip draft status in future PRs, please include [ready] in your PR title or add the skip-draft-status label when creating your PR.

[github-actions]

👋 Greetings, Airbyte Team Member!

Here are some helpful tips and reminders for your convenience.

💡 Show Tips and Tricks

PR Slash Commands

Airbyte Maintainers (that's you!) can execute the following slash commands on your PR:

• 🛠️ Quick Fixes
  • /format-fix - Fixes most formatting issues.
  • /bump-version - Bumps connector versions, scraping changelog description from the PR title.
    • Bump types: patch (default), minor, major, major_rc, rc, promote.
    • The rc type is a smart default: applies minor_rc if stable, or bumps the RC number if already RC.
    • The promote type strips the RC suffix to finalize a release.
    • Example: /bump-version type=rc or /bump-version type=minor
  • /bump-progressive-rollout-version - Alias for /bump-version type=rc. Bumps with an RC suffix and enables progressive rollout.
• ❇️ AI Testing and Review (internal link: AI-SDLC Docs):
  • /ai-prove-fix - Runs prerelease readiness checks, including testing against customer connections.
  • /ai-canary-prerelease - Rolls out prerelease to 5-10 connections for canary testing.
  • /ai-review - AI-powered PR review for connector safety and quality gates.
• 📝 AI Documentation:
  • /ai-docs-review - AI-powered documentation review for PRs with connector changes.
  • /ai-create-docs-pr - Creates a documentation PR for connector changes, stacked on the current PR.
• 🚀 Connector Releases:
  • /publish-connectors-prerelease - Publishes pre-release connector builds (tagged as {version}-preview.{git-sha}) for all modified connectors in the PR.
  • /enable-autopilot-rollouts - Enables autopilot progressive rollouts for the modified connector(s) in the PR, remediating "autopilot rollouts not enabled for {connector-name}" auto-merge blockers. Sets defaultRolloutMode: autopilot and enableProgressiveRollout: true, preserving any existing autopilotConfig.
    • Optional args: connector=<CONNECTOR_NAME> (defaults to the modified connectors in the PR), strategy=fast|slow|default (defaults to fast).
    • Example: /enable-autopilot-rollouts or /enable-autopilot-rollouts connector=source-faker strategy=slow
• ☕️ JVM connectors:
  • /update-connector-cdk-version connector=<CONNECTOR_NAME> - Updates the specified connector to the latest CDK version.
    Example: /update-connector-cdk-version connector=destination-bigquery
• 🐍 Python connectors:
  • /poe connector source-example lock - Run the Poe lock task on the source-example connector, committing the results back to the branch.
  • /poe source example lock - Alias for /poe connector source-example lock.
  • /poe source example use-cdk-branch my/branch - Pin the source-example CDK reference to the branch name specified.
  • /poe source example use-cdk-latest - Update the source-example CDK dependency to the latest available version.
• ⚙️ Admin commands:
  • /force-merge reason="<REASON>" - Force merges the PR using admin privileges, bypassing CI checks. Requires a reason.
    Example: /force-merge reason="CI is flaky, tests pass locally"

📚 Show Repo Guidance

Helpful Resources

• Breaking Changes Guide - Breaking changes, migration guides, and upgrade deadlines
• Developing Connectors Locally
• Managing Connector Secrets
• On-Demand Regression Tests
• #connector-ci-issues
• #connector-publish-updates
• #connector-build-statuses

📝 Edit this welcome message.

[github-actions]

Note

Autopilot progressive rollouts are not enabled for the following modified connector(s):

• source-gong

This is a courtesy heads-up only — it does not block merge or fail any check.
To enable automatic progressive rollouts for the connector(s) above, comment
/enable-autopilot-rollouts on this PR. This sets defaultRolloutMode: autopilot
and enableProgressiveRollout: true in each connector's metadata.yaml,
preserving any existing autopilotConfig.

[github-actions]

source-gong Connector Test Results

16 tests   13 ✅  12s ⏱️
 2 suites   3 💤
 2 files     0 ❌

Results for commit 0c9949a.

[devin-ai-integration]

Note on the one failing check: source-gong Pre-Release Checks fails on Connector Version Increment Check (master 1.3.2 == branch 1.3.2). This is intentional — the diff is metadata documentation URLs only, with no runtime, spec, or schema impact, so publishing a new connector version would be noise. Same precedent as #82265 (source-github docs-URL fix), which merged without a bump. The metadata validator itself passed, confirming api_release_history and api_deprecations are valid externalDocumentationUrls types. Happy to add a patch bump + changelog entry if a maintainer prefers a green board.

---

Devin session