Skip to content

Conversation

@devin-ai-integration
Copy link
Contributor

What

Updates the qa-checks.md file generation path to reflect the Docusaurus multi-instance structure migration. The file was previously generated at docs/contributing-to-airbyte/resources/qa-checks.md but needed to be moved to docs/community/contributing-to-airbyte/resources/qa-checks.md to align with the new multi-instance documentation structure where community docs live under the docs/community/ directory.

Requested by: @ian-at-airbyte
Link to Devin run: https://app.devin.ai/sessions/1615d4a9393940ebb574182b7ba0bd29

How

  1. Updated generation tooling:

    • Modified integration test constant to reference new path: docs/community/contributing-to-airbyte/resources/qa-checks.md
    • Updated template header comment with correct regeneration command
    • Updated README.md documentation with correct command
  2. Updated all versioned doc links (versions 1.6, 1.7, 1.8, 2.0):

    • Changed relative links like ./resources/qa-checks.md to absolute path /community/contributing-to-airbyte/resources/qa-checks
    • Updated links in change-cdk-connector.md, writing-connector-docs.md, testing-connectors/README.md, and connector-breaking-changes.md
  3. Regenerated documentation:

    • Ran connectors-qa generate-documentation docs/community/contributing-to-airbyte/resources/qa-checks.md
    • Deleted old file at docs/contributing-to-airbyte/resources/qa-checks.md

Review guide

Critical items to verify:

  1. Page accessibility: Visit https://docs.airbyte.com/community/contributing-to-airbyte/resources/qa-checks after deployment to confirm the page is accessible at the intended URL

  2. Link resolution in versioned docs: Check that the absolute path links /community/contributing-to-airbyte/resources/qa-checks resolve correctly from the versioned platform docs (1.6, 1.7, 1.8, 2.0)

  3. Generated file content:

    • docs/community/contributing-to-airbyte/resources/qa-checks.md - Note that some content changed during regeneration (last section changed from "Testing" to "Version", and some links changed from absolute GitHub URLs to relative paths). Verify these changes are expected.
  4. Generation tooling:

    • airbyte-ci/connectors/connectors_qa/src/connectors_qa/templates/qa_checks.md.j2 - Template header comment
    • airbyte-ci/connectors/connectors_qa/tests/integration_tests/test_documentation.py - Integration test passes locally
    • airbyte-ci/connectors/connectors_qa/README.md - Documentation updated
  5. Sidebar navigation: Verify that sidebar navigation in docusaurus/sidebar-community.js correctly references the doc and navigation works as expected

Less critical but worth checking:

  • Search for any other references to the old path that might have been missed
  • Run a local Docusaurus build (cd docusaurus && pnpm clear && pnpm build) to catch any broken links

User Impact

Users will now find the QA checks documentation at the correct location within the community documentation section, aligned with the multi-instance Docusaurus structure. All links to this documentation from versioned platform docs have been updated to point to the new location using absolute paths to avoid cross-instance navigation issues.

Potential negative impacts:

  • External documentation or bookmarks pointing to the old URL path will need to be updated
  • If there are any missed references to the old path, they will result in broken links

Can this PR be safely reverted and rolled back?

  • YES 💚

This change is purely documentation-related and can be safely reverted. The old file was deleted but can be restored from git history if needed. The integration test validates that the generation process works correctly with the new path.

…nce structure

- Update integration test to reference new path: docs/community/contributing-to-airbyte/resources/qa-checks.md
- Update template header comment with correct regeneration command
- Update README.md with correct generation command
- Update all versioned docs (1.6, 1.7, 1.8, 2.0) to use absolute path /community/contributing-to-airbyte/resources/qa-checks
- Regenerate documentation at new location
- Remove old file at docs/contributing-to-airbyte/resources/qa-checks.md

Co-Authored-By: [email protected] <[email protected]>
@devin-ai-integration
Copy link
Contributor Author

Original prompt from [email protected]
@Devin can you investigate the generation of the file airbyte: docs/contributing-to-airbyte/resources/qa-checks.md.

I'd like to know:

• What process generates it?
• How can I reconfigure that process to generate the file to a different location? I'd like it to go here: <https://docs.airbyte.com/community/contributing-to-airbyte/resources/qa-checks> 
Thread URL: https://airbytehq-team.slack.com/archives/D08FX8EC9L0/p1762286664830729

@devin-ai-integration
Copy link
Contributor Author

🤖 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 and CI monitoring

@github-actions
Copy link
Contributor

github-actions bot commented Nov 4, 2025

👋 Greetings, Airbyte Team Member!

Here are some helpful tips and reminders for your convenience.

Helpful Resources

PR Slash Commands

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

  • /format-fix - Fixes most formatting issues.
  • /bump-version - Bumps connector versions.
    • You can specify a custom changelog by passing changelog. Example: /bump-version changelog="My cool update"
    • Leaving the changelog arg blank will auto-populate the changelog from the PR title.
  • /run-cat-tests - Runs legacy CAT tests (Connector Acceptance Tests)
  • /build-connector-images - Builds and publishes a pre-release docker image for the modified connector(s).
  • 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
    • /bump-bulk-cdk-version type=patch changelog='foo' - Bump the Bulk CDK's version. type can be major/minor/patch.
  • 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.

📝 Edit this welcome message.

Replace docId references to 'contributing-to-airbyte/resources/qa-checks' with link items pointing to '/community/contributing-to-airbyte/resources/qa-checks' in all platform versioned sidebars (1.6, 1.7, 1.8, 2.0).

This fixes the Docusaurus build failure caused by cross-instance doc references after the file moved from the platform plugin to the community plugin.

Co-Authored-By: [email protected] <[email protected]>
Address PR feedback:
1. Fix generator templates to use absolute GitHub URLs instead of relative paths
   - Updated documentation_headers_check_description.md.j2
   - Updated section_content_description.md.j2
   - This fixes the broken link issue in the generated qa-checks.md

2. Update versioned docs to use site-root links (/community/...) instead of full URLs
   - Changed https://docs.airbyte.com/community/... to /community/...
   - Updated versions 1.6, 1.7, 1.8, and 2.0

3. Regenerate qa-checks.md with fixed templates
   - All 'standard template' links now use absolute GitHub URLs
   - Integration test passes successfully

Co-Authored-By: [email protected] <[email protected]>
@devin-ai-integration
Copy link
Contributor Author

Good catch! I've fixed this by updating the generator templates to always use absolute GitHub URLs instead of relative paths.

The issue was that the relative link ../../../airbyte-ci/... became broken when the generated file moved from docs/contributing-to-airbyte/resources/qa-checks.md to docs/community/contributing-to-airbyte/resources/qa-checks.md (one level deeper in the directory structure).

Changes made:

  • Updated documentation_headers_check_description.md.j2 to use https://github.com/airbytehq/airbyte/blob/master/...
  • Updated section_content_description.md.j2 to use the same absolute GitHub URL
  • Regenerated qa-checks.md with the fixed templates

The generated documentation now has working links to the standard template on GitHub.

@devin-ai-integration
Copy link
Contributor Author

Agreed! I've updated all the versioned docs to use site-root links instead of full URLs.

Changes made:

  • Changed https://docs.airbyte.com/community/contributing-to-airbyte/resources/qa-checks to /community/contributing-to-airbyte/resources/qa-checks
  • Updated in versions 1.6, 1.7, 1.8, and 2.0
  • Files updated:
    • connector-development/testing-connectors/README.md (all versions)
    • connector-development/writing-connector-docs.md (versions 1.6, 1.7)
    • contributing-to-airbyte/change-cdk-connector.md (versions 1.6, 1.7, 1.8)
    • connector-development/connector-breaking-changes.md (version 2.0)

This follows the standard Docusaurus practice of using site-root links for internal documentation references.

@github-actions
Copy link
Contributor

github-actions bot commented Nov 4, 2025

Deploy preview for airbyte-docs ready!

✅ Preview
https://airbyte-docs-kk4bzdgxn-airbyte-growth.vercel.app

Built with commit af84a01.
This pull request is being automatically deployed with vercel-action

@ian-at-airbyte
Copy link
Contributor

ian-at-airbyte commented Nov 5, 2025

(aside) Commentary for reviewers:

I noticed the way we generate public docs for connector QA tests didn't populate to the right place anymore (IE this doc: https://docs.airbyte.com/community/contributing-to-airbyte/resources/qa-checks). This file was out of date, while the docs generation script updated an orphaned file that didn't get built in the public docs.

This broke after I migrated Docusaurus from a single instance to a multi-instance deployment ~6 months ago. I moved the location of the public docs, but didn't think to do the work that's been done here.

I also noticed the generated public docs contained broken links because the Jinja templates used relative links that didn't work on the public web.

The objective of this PR is to:

  1. Ensure we can run the doc generation and populate the correct documentation file that people see
  2. Avoid putting broken links into public docs by switching Jinja templates to use absolute links that work from any location.
  3. Update the test that requires that public doc to exist in a certain location.

It updates the test, the checks themselves, and the output doc in Docusaurus, which should now have the latest version of the checks.

What matters:

  • Everything in /airbyte-ci/**
  • Everything in /docs/**: Updates the actual documentation with the latest checks, and deletes the old orphaned doc from the old location.

What doesn't matter:

  • Everything in /docusaurus/. Those are just link updates in docs for older Airbyte versions. Since the build succeeded, we can assume they work.

@ian-at-airbyte ian-at-airbyte added area/documentation Improvements or additions to documentation team/documentation labels Nov 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/documentation Improvements or additions to documentation team/documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants