Skip to content

return each record inside {data} #20

return each record inside {data}

return each record inside {data} #20

Triggered via pull request September 29, 2023 02:48
Status Failure
Total duration 17s
Artifacts
Require Connector Merge Checklist Job
6s
Require Connector Merge Checklist Job
Fit to window
Zoom out
Zoom in

Annotations

3 errors
Require Connector Merge Checklist Job
All checklist items not checked. Review your PR description and comments for unchecked items.
Require Connector Merge Checklist Job
Process completed with exit code 1.
Require Connector Merge Checklist Job
The following items are not marked as completed: PR name follows [PR naming conventions](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#pull-request-title-convention), [Breaking changes are considered](https://docs.airbyte.com/contributing-to-airbyte/change-cdk-connector/#breaking-changes-to-connectors). If a **Breaking Change** is being introduced, ensure an Airbyte engineer has created a Breaking Change Plan., Connector version has been incremented in the Dockerfile and metadata.yaml according to our [Semantic Versioning for Connectors](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#semantic-versioning-for-connectors) guidelines, You've updated the connector's `metadata.yaml` file any other relevant changes, including a `breakingChanges` entry for major version bumps. See [metadata.yaml docs](https://docs.airbyte.com/connector-development/connector-metadata-file/), Secrets in the connector's spec are annotated with `airbyte_secret`, All documentation files are up to date. (README.md, bootstrap.md, docs.md, etc...), Changelog updated in `docs/integrations/<source or destination>/<name>.md` with an entry for the new version. See changelog [example](https://docs.airbyte.io/integrations/sources/stripe#changelog), Migration guide updated in `docs/integrations/<source or destination>/<name>-migrations.md` with an entry for the new version, if the version is a breaking change. See migration guide [example](https://docs.airbyte.io/integrations/sources/faker-migrations), If set, you've ensured the icon is present in the `platform-internal` repo. ([Docs](https://docs.airbyte.com/connector-development/connector-metadata-file/#the-icon-field))