docusaurus/platform_versioned_docs/version-2.0/contributing-to-airbyte/README.md
Thank you for your interest in contributing! Contributions are very welcome. We appreciate first time contributors and we are happy help you get started. Join our community Slack and feel free to reach out with questions in #dev-and-contribuions channel.
If you're interacting in Slack, codebases, mailing lists, events, or any other Airbyte activity, you must follow the Code of Conduct. Please review it before getting started.
Most of the issues that are open for contributions are tagged with good first issue or help-welcome.
If you are interested in an issue that isn't tagged, post a comment with your approach, and we'd be happy to assign it to you. If you submit a fix isn't linked to an issue you're assigned, there is chance Airbyte won't accept it.
Airbyte evaluates contributions outside this scope on a case-by-case basis. Reach out to the Airbyte team before starting to ensure the team can accept your idea.
Contributions to Airbyte connectors may take some time to review, as they can affect many users. To assist us during code review, include as much information as possible in your pull request, including examples, use cases, documentation links, and more.
:::warning Airbyte is revamping its core Java destinations codebase. We're not reviewing/accepting new Java connectors at this time. :::
airbyte repository.{YOUR_USERNAME}/{FEATURE/BUG} (e.g. jdoe/source-stock-api-stream-fix)needs triage label to your Pull Request. Pull requests without an issue attached take longer to review.You can check the status of your contribution in this Github Project. It will provide you what Sprint your contribution was assigned and when you can expect a review.
When submitting a pull request, please ensure that Airbyte maintainers have write access to your branch. This allows us to apply formatting fixes, security-related patches, and dependency updates directly, which significantly speeds up the review and approval process.
To enable write access on your PR from Airbyte maintainers, please check the "Allow edits from maintainers" box when submitting from your PR. You must also create your PR from a fork in your personal GitHub account rather than an organization account, or else you will not see this option. The requirement to create from your personal fork is based on GitHub's additional security restrictions for PRs created from organization forks. For more information about the GitHub security model, please see the GitHub documentation page regarding PRs from forks.
For more details on contribution requirements, please see our contribution workflow documentation.
:::warning Do not submit a pull request using the default branch of your forked repository. This will block Airbyte maintainers from pushing changes to your branch. :::
Guidelines for connector contributions included in the Connector Development Guide:
We welcome all pull requests that clarify concepts, fix typos and grammar, and improve the structure of Airbyte's documentation. Check the Updating Documentation guide for details on submitting documentation changes.
For examples of good connector docs, see the Salesforce source connector and Snowflake destination connector docs.
We welcome contributions as new tutorials / showcases / articles, or as enhancements to any of the existing guides on our tutorials page. Head to this repo dedicated to community content: Write for the Community.
Feel free to submit a pull request in this repo, if you have something to add even if it's not related to anything mentioned above.
Another crucial way to contribute is by reporting bugs and helping other users in the community. You're welcome to join the Community Slack. Refer to our Issues and Feature Requests guide to learn about the best ways to report bugs.