Hi, what is the process for getting started? I've ...
# help-connector-development
a
Hi, what is the process for getting started? I've made some PRs but they just sit there. 1. Where can I ask for guidance? 2. Where can I get an overview of the process of submitting a PR, getting a new docker image version, and getting merged?
k
A message from kapa.ai
Hi! I understand that you have submitted some PRs and are looking for guidance on the process. Here's an overview of the process for submitting a PR, getting a new Docker image version, and getting merged: 1. Asking for guidance: If you need help with any step of the process or have questions, you can submit a PR with your progress and any questions you have. You can also ask for guidance on the [Airbyte Slack](https://slack.airbyte.com) or the [Airbyte forum](https://discuss.airbyte.io). 2. Overview of the process: - Submit a PR: Once you have validated that your connector is working as expected, you can push your local branch to GitHub and create a pull request. An Airbyte engineer will work with you to get your connector merged into the master branch so that it can be distributed and used by others [source](https://airbyte.com/tutorials/extract-data-from-the-webflow-api). - Run integration tests: Coordinate with an Airbyte engineer (via the PR) to add test credentials so that integration tests can be run for the connector in the CI [source](https://docs.airbyte.com/connector-development/tutorials/building-a-python-source). - Publish Docker image: To publish a Docker image, you can use the
/publish
command in a comment on your PR, like this:
/publish connector=connectors/source-sendgrid
. This will publish the Docker image if it doesn't exist for a single connector on the latest PR commit [source](https://docs.airbyte.com/connector-development/testing-connectors/legacy-standard-source-tests). - Review process: Airbyte engineers will review your PR, checking if it solves the issue, if the proposed solution is reasonable, if it's tested, and if it introduces any security risks. Once your PR passes, it will be merged [source](https://docs.airbyte.com/contributing-to-airbyte). Please note that the review process might take some time, but you can always reach out to the Airbyte team on [Slack](https://slack.airbyte.com) or in the PR comments for updates on your PR status.
a
This doesn't happen: "An Airbyte engineer will work with you to get your connector merged into the master branch"
How can I get better engagement?
This doesn't happen: "An Airbyte engineer will work with you to get your connector merged into the master branch" @kapa.ai
k
A message from kapa.ai
m
Adam can you post in #C054V9JFTC6
k
I understand your concern. In the [extract from a previous support conversation on Slack](https://airbytehq.slack.com/archives/C021JANJ6TY/p1661852356559589), it was mentioned that an Airbyte engineer would work with the contributor to get their connector merged into the master branch. However, there might be delays or other factors affecting the review process. Please be patient, and if you have any concerns or need assistance, you can reach out to the Airbyte team on their [Slack channel](https://airbytehq.slack.com) or [discuss forum](https://discuss.airbyte.io). They are usually responsive and will help you through the process.
a
Thanks, I will look there @Marcos Marx (Airbyte)