source-ticktick contribution from luutuankiet

[luutuankiet]

What

This PR adds a new connector for source ticktick (source-ticktick).

Contributor-provided connector description:

Source for the ticktick openapi endpoint at https://developer.ticktick.com/

The contributor provided the following description of the change:

Extracts 2 endpoints : Project and Tasks

Details

Expand for list of spec properties and streams

Configuration

Input	Type	Description	Default Value
api_key	string	API Key optained from running the workflow get access token

Streams

Stream Name	Primary Key	Pagination	Supports Full Sync	Supports Incremental
projects	id	No pagination	✅	❌
tasks	id	No pagination	✅	❌

Reviewer checklist

• Consider how the connector handles pagination (docs).
• Help the contributor upload an icon that follows our icon design guidelines
• Click into the CI workflows that wait for a maintainer to run them, which should trigger CI runs

[vercel]

@luutuankiet is attempting to deploy a commit to the Airbyte Growth Team on Vercel.

A member of the Team first needs to authorize it.

[CLAassistant]

All committers have signed the CLA.

[github-actions]

👋 Welcome to Airbyte!

Thank you for your contribution from luutuankiet/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. "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.

[cgardens]

thanks for your contribution. please address the CI error and we can get this merged!

source-ticktick - ❌ Failed - Connectors must have an icon: Icon file is the default Airbyte icon. Please replace it with a custom square icon.
Error: 1 checks failed

[luutuankiet]

/run-connector-tests

[luutuankiet]

hi @cgardens the errors have been resolved!

[cgardens]

/run-connector-tests

Connector CI Tests Started

These tests will leverage Airbyte's integration test credentials.

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

[cgardens]

Thanks for your contribution!