Skip to content

docs: fix dead sample-connector manifest links in low-code CDK docs - #88468

Merged
Patrick Nilan (pnilan) merged 1 commit into
airbytehq:masterfrom
Shahzeb-DataEngineer:docs/fix-dead-connector-links
Oct 14, 2026
Merged

Patrick Nilan (pnilan) merged 1 commit into
airbytehq:masterfrom
Shahzeb-DataEngineer:docs/fix-dead-connector-links

Conversation

@Shahzeb-DataEngineer

Copy link
Copy Markdown
Contributor

Description

Fixes the dead sample-connector links reported in #69164. The three links in the
"Sample connectors" section of the low-code CDK overview pointed at a nested directory
level (e.g. airbyte-integrations/connectors/source-greenhouse/source_greenhouse/manifest.yaml)
that no longer exists since connectors were restructured to keep manifest.yaml at the
connector root. All three now point at the connector root:

  • source-greenhouse/manifest.yaml
  • source-sendgrid/manifest.yaml
  • source-sentry/manifest.yaml

While at it, fixed the same broken pattern in the file-syncing doc
(source-zendesk-support/source_zendesk_support/manifest.yaml 404s the same way).

Verified each corrected path against master (the manifest.yaml files exist at the
connector roots).

Related Issue

closes #69164

The sample-connector links pointed at a nested directory level (e.g.
source-greenhouse/source_greenhouse/manifest.yaml) that no longer exists
since connectors were restructured to keep manifest.yaml at the connector
root. Fixes the 404s reported in airbytehq#69164, plus the same broken pattern in
the file-syncing doc (source-zendesk-support).

Signed-off-by: Shahzeb Ali <[email protected]>
Copilot AI balanced review requested due to automatic review settings October 12, 2026 04:49

Copilot AI 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.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@CLAassistant

CLAassistant commented Oct 12, 2026 •

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

@octavia-bot

octavia-bot Bot commented Oct 12, 2026

Copy link
Copy Markdown
Contributor

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

Copy link
Copy Markdown
Contributor

👋 Welcome to Airbyte!

Thank you for your contribution from Shahzeb-DataEngineer/airbyte! We're excited to have you in the Airbyte community.

If you have any questions, feel free to ask in the PR comments or join our Slack community.

💡 Show Tips and Tricks

PR Slash Commands

As needed or by request, Airbyte Maintainers can execute the following slash commands on your PR:

  • /format-fix - Fixes most formatting issues.
  • /bump-version - Bumps connector versions.
  • /run-connector-tests - Runs connector tests.
  • /run-cat-tests - Runs CAT tests.
  • /run-regression-tests - Runs regression tests for the modified connector(s).
  • /build-connector-images - Builds and publishes a pre-release docker image for the modified connector(s).
  • /publish-connectors-prerelease - Publishes pre-release connector builds (tagged as {version}-preview.{git-sha}) for all modified connectors in the PR.
  • /ai-review - AI-powered PR review for connector safety and quality gates.
  • /ai-docs-review - AI-powered documentation review for PRs with connector changes.
  • /ai-create-docs-pr - Creates a documentation PR for connector changes.
  • /force-merge reason="<A_GOOD_REASON>" - Force merges the PR using admin privileges, bypassing CI checks. Requires a reason.

Tips for Working with CI

  1. Pre-Release Checks. Please pay attention to these, as they contain standard checks on the metadata.yaml file, docs requirements, etc. If you need help resolving a pre-release check, please ask a maintainer.
    • Note: If you are creating a new connector, please be sure to replace the default logo.svg file with a suitable icon.
  2. Connector CI Tests. Some failures here may be expected if your tests require credentials. Please review these results to ensure (1) unit tests are passing, if applicable, and (2) integration tests pass to the degree possible and expected.
  3. (Optional.) BYO Connector Credentials for tests in your fork. You can optionally set up your fork with BYO credentials for your connector. This can significantly speed up your review, ensuring your changes are fully tested before the maintainers begin their review.
📚 Show Repo Guidance

Helpful Resources

📝 Edit this welcome message.

@Shahzeb-DataEngineer
Shahzeb Ali (Shahzeb-DataEngineer) marked this pull request as ready for review October 13, 2026 07:40
@github-project-automation github-project-automation Bot moved this from New PRs to Ready to Ship in 🧑‍🏭 Community Pull Requests Oct 14, 2026
@pnilan

Copy link
Copy Markdown
Member

Thanks for the fix Shahzeb Ali (@Shahzeb-DataEngineer) !

@pnilan
Patrick Nilan (pnilan) merged commit 54da305 into airbytehq:master Oct 14, 2026
53 checks passed
@github-project-automation github-project-automation Bot moved this from Ready to Ship to Done in 🧑‍🏭 Community Pull Requests Oct 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Development

Successfully merging this pull request may close these issues.

[Docs]: Sample connector links are dead

4 participants