AJ's community PR test (do not merge)

[Aaron ("AJ") Steers (aaronsteers)]

Demo/test PR of new Community CI workflows, including BYO Creds.

[vercel]

Aaron ("AJ") Steers (@aaronsteers) is attempting to deploy a commit to the Airbyte Growth Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
airbyte-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 20, 2025 1:19am

[github-actions]

👋 Welcome to Airbyte!

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

Helpful Resources

• PR Guidelines: Check our guidelines for contributions.
• Developing Connectors Locally: Learn how to set up your environment and develop connectors locally.
• If you enable BYO Connector Credentials within your fork, you can view your test results here.

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.

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

[Aaron ("AJ") Steers (aaronsteers)]

/run-connector-tests

[Aaron ("AJ") Steers (aaronsteers)]

/run-connector-tests

[Aaron ("AJ") Steers (aaronsteers)]

/run-connector-tests

[Aaron ("AJ") Steers (aaronsteers)]

/run-connector-tests

Connector CI Tests job started... Check job output.
Connector CI Tests job completed. See logs for details.

[Aaron ("AJ") Steers (aaronsteers)]

/run-connector-tests

Connector CI Tests Started

These tests will leverage Airbyte's integration test credentials.

Check job output.
Connector CI Tests job completed. See logs for details.

[Aaron ("AJ") Steers (aaronsteers)]

/run-cat-tests

[github-actions]

👋 Welcome to Airbyte!

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

Helpful Resources

• PR Guidelines: Check our guidelines for contributions.
• Developing Connectors Locally: Learn how to set up your environment and develop connectors locally.
• If you enable BYO Connector Credentials within your fork, you can view your test results here:
  

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.

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

Tips for Working with CI

1. "Vercel" CI failures. You can always ignore these. These are our docs builds but they can only be run by approval. A maintainer will approve the workflow upon request, but this failure should not be of concern.
2. 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.
3. 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.
4. (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.

[Copilot]

Pull Request Overview

This is a demo/test PR for new Community CI workflows that includes dummy commits to test the workflow functionality. The PR adds temporary comment lines to connector metadata files for testing purposes.

• Adds dummy comments to connector metadata files for CI workflow testing
• Includes "todo: revert-me" notes indicating these are temporary changes for testing

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
airbyte-integrations/connectors/source-klaviyo/metadata.yaml	Adds dummy comment for CI workflow testing
airbyte-integrations/connectors/destination-teradata/metadata.yaml	Adds dummy comment for CI workflow testing

[github-actions]

👋 Welcome to Airbyte!

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

Helpful Resources

• PR Guidelines: Check our guidelines for contributions.
• Developing Connectors Locally: Learn how to set up your environment and develop connectors locally.
• If you enable BYO Connector Credentials within your fork, you can view your test results here:
  

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.
• /build-connector-images - Builds and publishes a pre-release docker image for the modified connector(s).

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

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.