airbyte-source-github 1.5.7__tar.gz → 1.6.1__tar.gz

airbyte_source_github-1.6.1/PKG-INFO

@@ -0,0 +1,111 @@
+Metadata-Version: 2.1
+Name: airbyte-source-github
+Version: 1.6.1
+Summary: Source implementation for Github.
+Home-page: https://airbyte.com
+License: MIT
+Author: Airbyte
+Author-email: contact@airbyte.io
+Requires-Python: >=3.9,<3.12
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Requires-Dist: airbyte-cdk (==0.60.1)
+Requires-Dist: sgqlc (==16.3)
+Project-URL: Documentation, https://docs.airbyte.com/integrations/sources/github
+Project-URL: Repository, https://github.com/airbytehq/airbyte
+Description-Content-Type: text/markdown
+
+# Github source connector
+
+
+This is the repository for the Github source connector, written in Python.
+For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.com/integrations/sources/github).
+
+## Local development
+
+### Prerequisites
+* Python (~=3.9)
+* Poetry (~=1.7) - installation instructions [here](https://python-poetry.org/docs/#installation)
+
+
+### Installing the connector
+From this connector directory, run:
+```bash
+poetry install --with dev
+```
+
+
+### Create credentials
+**If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.com/integrations/sources/github)
+to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_github/spec.yaml` file.
+Note that any directory named `secrets` is gitignored across the entire Airbyte repo, so there is no danger of accidentally checking in sensitive information.
+See `sample_files/sample_config.json` for a sample config file.
+
+
+### Locally running the connector
+```
+poetry run source-github spec
+poetry run source-github check --config secrets/config.json
+poetry run source-github discover --config secrets/config.json
+poetry run source-github read --config secrets/config.json --catalog sample_files/configured_catalog.json
+```
+
+### Running unit tests
+To run unit tests locally, from the connector directory run:
+```
+poetry run pytest unit_tests
+```
+
+### Building the docker image
+1. Install [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md)
+2. Run the following command to build the docker image:
+```bash
+airbyte-ci connectors --name=source-github build
+```
+
+An image will be available on your host with the tag `airbyte/source-github:dev`.
+
+
+### Running as a docker container
+Then run any of the connector commands as follows:
+```
+docker run --rm airbyte/source-github:dev spec
+docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-github:dev check --config /secrets/config.json
+docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-github:dev discover --config /secrets/config.json
+docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-github:dev read --config /secrets/config.json --catalog /integration_tests/configured_catalog.json
+```
+
+### Running our CI test suite
+You can run our full test suite locally using [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md):
+```bash
+airbyte-ci connectors --name=source-github test
+```
+
+### Customizing acceptance Tests
+Customize `acceptance-test-config.yml` file to configure acceptance tests. See [Connector Acceptance Tests](https://docs.airbyte.com/connector-development/testing-connectors/connector-acceptance-tests-reference) for more information.
+If your connector requires to create or destroy resources for use during acceptance tests create fixtures for it and place them inside integration_tests/acceptance.py.
+
+### Dependency Management
+All of your dependencies should be managed via Poetry. 
+To add a new dependency, run:
+```bash
+poetry add <package-name>
+```
+
+Please commit the changes to `pyproject.toml` and `poetry.lock` files.
+
+## Publishing a new version of the connector
+You've checked out the repo, implemented a million dollar feature, and you're ready to share your changes with the world. Now what?
+1. Make sure your changes are passing our test suite: `airbyte-ci connectors --name=source-github test`
+2. Bump the connector version (please follow [semantic versioning for connectors](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#semantic-versioning-for-connectors)): 
+    - bump the `dockerImageTag` value in in `metadata.yaml`
+    - bump the `version` value in `pyproject.toml`
+3. Make sure the `metadata.yaml` content is up to date.
+4. Make sure the connector documentation and its changelog is up to date (`docs/integrations/sources/github.md`).
+5. Create a Pull Request: use [our PR naming conventions](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#pull-request-title-convention).
+6. Pat yourself on the back for being an awesome contributor.
+7. Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.
+8. Once your PR is merged, the new version of the connector will be automatically published to Docker Hub and our connector registry.

airbyte_source_github-1.6.1/README.md

@@ -0,0 +1,91 @@
+# Github source connector
+
+
+This is the repository for the Github source connector, written in Python.
+For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.com/integrations/sources/github).
+
+## Local development
+
+### Prerequisites
+* Python (~=3.9)
+* Poetry (~=1.7) - installation instructions [here](https://python-poetry.org/docs/#installation)
+
+
+### Installing the connector
+From this connector directory, run:
+```bash
+poetry install --with dev
+```
+
+
+### Create credentials
+**If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.com/integrations/sources/github)
+to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_github/spec.yaml` file.
+Note that any directory named `secrets` is gitignored across the entire Airbyte repo, so there is no danger of accidentally checking in sensitive information.
+See `sample_files/sample_config.json` for a sample config file.
+
+
+### Locally running the connector
+```
+poetry run source-github spec
+poetry run source-github check --config secrets/config.json
+poetry run source-github discover --config secrets/config.json
+poetry run source-github read --config secrets/config.json --catalog sample_files/configured_catalog.json
+```
+
+### Running unit tests
+To run unit tests locally, from the connector directory run:
+```
+poetry run pytest unit_tests
+```
+
+### Building the docker image
+1. Install [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md)
+2. Run the following command to build the docker image:
+```bash
+airbyte-ci connectors --name=source-github build
+```
+
+An image will be available on your host with the tag `airbyte/source-github:dev`.
+
+
+### Running as a docker container
+Then run any of the connector commands as follows:
+```
+docker run --rm airbyte/source-github:dev spec
+docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-github:dev check --config /secrets/config.json
+docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-github:dev discover --config /secrets/config.json
+docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-github:dev read --config /secrets/config.json --catalog /integration_tests/configured_catalog.json
+```
+
+### Running our CI test suite
+You can run our full test suite locally using [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md):
+```bash
+airbyte-ci connectors --name=source-github test
+```
+
+### Customizing acceptance Tests
+Customize `acceptance-test-config.yml` file to configure acceptance tests. See [Connector Acceptance Tests](https://docs.airbyte.com/connector-development/testing-connectors/connector-acceptance-tests-reference) for more information.
+If your connector requires to create or destroy resources for use during acceptance tests create fixtures for it and place them inside integration_tests/acceptance.py.
+
+### Dependency Management
+All of your dependencies should be managed via Poetry. 
+To add a new dependency, run:
+```bash
+poetry add <package-name>
+```
+
+Please commit the changes to `pyproject.toml` and `poetry.lock` files.
+
+## Publishing a new version of the connector
+You've checked out the repo, implemented a million dollar feature, and you're ready to share your changes with the world. Now what?
+1. Make sure your changes are passing our test suite: `airbyte-ci connectors --name=source-github test`
+2. Bump the connector version (please follow [semantic versioning for connectors](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#semantic-versioning-for-connectors)): 
+    - bump the `dockerImageTag` value in in `metadata.yaml`
+    - bump the `version` value in `pyproject.toml`
+3. Make sure the `metadata.yaml` content is up to date.
+4. Make sure the connector documentation and its changelog is up to date (`docs/integrations/sources/github.md`).
+5. Create a Pull Request: use [our PR naming conventions](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#pull-request-title-convention).
+6. Pat yourself on the back for being an awesome contributor.
+7. Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.
+8. Once your PR is merged, the new version of the connector will be automatically published to Docker Hub and our connector registry.

airbyte_source_github-1.6.1/pyproject.toml

@@ -0,0 +1,36 @@
+[build-system]
+requires = [
+    "poetry-core>=1.0.0",
+]
+build-backend = "poetry.core.masonry.api"
+
+[tool.poetry]
+version = "1.6.1"
+name = "airbyte-source-github"
+description = "Source implementation for Github."
+authors = [
+    "Airbyte <contact@airbyte.io>",
+]
+license = "MIT"
+readme = "README.md"
+documentation = "https://docs.airbyte.com/integrations/sources/github"
+homepage = "https://airbyte.com"
+repository = "https://github.com/airbytehq/airbyte"
+packages = [
+    { include = "source_github" },
+]
+
+[tool.poetry.dependencies]
+python = "^3.9,<3.12"
+airbyte-cdk = "==0.60.1"
+sgqlc = "==16.3"
+
+[tool.poetry.scripts]
+source-github = "source_github.run:run"
+
+[tool.poetry.group.dev.dependencies]
+requests-mock = "^1.9.3"
+freezegun = "^1.2"
+pytest-mock = "^3.6.1"
+pytest = "^6.2"
+responses = "^0.23.1"

{airbyte-source-github-1.5.7 → airbyte_source_github-1.6.1}/source_github/schemas/collaborators.json

@@ -65,13 +65,19 @@
     "permissions": {
       "type": ["null", "object"],
       "properties": {
-        "pull": {
+        "admin": {
+          "type": ["null", "boolean"]
+        },
+        "maintain": {
           "type": ["null", "boolean"]
         },
         "push": {
           "type": ["null", "boolean"]
         },
-        "admin": {
+        "pull": {
+          "type": ["null", "boolean"]
+        },
+        "triage": {
           "type": ["null", "boolean"]
         }
       }

{airbyte-source-github-1.5.7 → airbyte_source_github-1.6.1}/source_github/schemas/issue_events.json

@@ -50,6 +50,99 @@
     "issue": {
       "type": ["null", "object"],
       "properties": {
+        "active_lock_reason": {
+          "type": ["null", "string"]
+        },
+        "assignee": {
+          "$ref": "user.json"
+        },
+        "assignees": {
+          "type": ["null", "array"],
+          "items": {
+            "$ref": "user.json"
+          }
+        },
+        "author_association": {
+          "type": ["null", "string"]
+        },
+        "closed_at": {
+          "type": ["null", "string"],
+          "format": "date-time"
+        },
+        "updated_at": {
+          "type": ["null", "string"],
+          "format": "date-time"
+        },
+        "comments": {
+          "type": ["null", "integer"]
+        },
+        "draft": {
+          "type": ["null", "boolean"]
+        },
+        "created_at": {
+          "type": ["null", "string"],
+          "format": "date-time"
+        },
+        "labels": {
+          "type": ["null", "array"],
+          "items": {
+            "type": ["null", "object"],
+            "properties": {
+              "id": {
+                "type": ["null", "integer"]
+              },
+              "node_id": {
+                "type": ["null", "string"]
+              },
+              "url": {
+                "type": ["null", "string"]
+              },
+              "name": {
+                "type": ["null", "string"]
+              },
+              "description": {
+                "type": ["null", "string"]
+              },
+              "color": {
+                "type": ["null", "string"]
+              },
+              "default": {
+                "type": ["null", "boolean"]
+              }
+            }
+          }
+        },
+        "locked": {
+          "type": ["null", "boolean"]
+        },
+        "milestone": {
+          "type": ["null", "object"]
+        },
+        "performed_via_github_app": {
+          "type": ["null", "object"]
+        },
+        "state_reason": {
+          "type": ["null", "string"]
+        },
+        "pull_request": {
+          "type": ["null", "object"],
+          "properties": {
+            "merged_at": {
+              "type": ["string", "null"],
+              "format": "date-time"
+            },
+            "diff_url": { "type": ["string", "null"] },
+            "html_url": { "type": ["string", "null"] },
+            "patch_url": { "type": ["string", "null"] },
+            "url": { "type": ["string", "null"] }
+          }
+        },
+        "timeline_url": {
+          "type": ["null", "string"]
+        },
+        "reactions": {
+          "$ref": "reactions.json"
+        },
         "id": {
           "type": ["null", "integer"]
         },

{airbyte-source-github-1.5.7 → airbyte_source_github-1.6.1}/source_github/schemas/issue_timeline_events.json

@@ -970,7 +970,7 @@
       "$ref": "events/reviewed.json"
     },
     "commented": {
-      "$ref": "events/commented.json"
+      "$ref": "events/comment.json"
     },
     "commit_commented": {
       "$ref": "events/commented.json"

{airbyte-source-github-1.5.7 → airbyte_source_github-1.6.1}/source_github/schemas/pull_requests.json

@@ -244,6 +244,9 @@
         },
         "repo_id": {
           "type": ["null", "integer"]
+        },
+        "user": {
+          "$ref": "user.json"
         }
       }
     },
@@ -264,6 +267,12 @@
         },
         "repo_id": {
           "type": ["null", "integer"]
+        },
+        "repo": {
+          "type": ["null", "object"]
+        },
+        "user": {
+          "$ref": "user.json"
         }
       }
     },

{airbyte-source-github-1.5.7 → airbyte_source_github-1.6.1}/source_github/schemas/repositories.json

@@ -306,6 +306,22 @@
               "type": ["null", "string"]
             }
           }
+        },
+        "secret_scanning_validity_checks": {
+          "type": ["null", "object"],
+          "properties": {
+            "status": {
+              "type": ["null", "string"]
+            }
+          }
+        },
+        "dependabot_security_updates": {
+          "type": ["null", "object"],
+          "properties": {
+            "status": {
+              "type": ["null", "string"]
+            }
+          }
         }
       }
     }

{airbyte-source-github-1.5.7 → airbyte_source_github-1.6.1}/source_github/schemas/shared/events/cross_referenced.json

@@ -43,6 +43,8 @@
           "description": "Issues are a great way to keep track of tasks, enhancements, and bugs for your projects.",
           "type": "object",
           "properties": {
+            "author_association": { "type": ["string", "null"] },
+            "performed_via_github_app": { "type": ["object", "null"] },
             "id": { "type": "integer" },
             "node_id": { "type": "string" },
             "url": { "type": "string" },
@@ -247,6 +249,7 @@
             "locked": { "type": "boolean" },
             "active_lock_reason": { "type": ["string", "null"] },
             "comments": { "type": "integer" },
+            "draft": { "type": ["boolean", "null"] },
             "pull_request": {
               "type": "object",
               "properties": {
@@ -775,6 +778,41 @@
                   }
                 }
               }
+            },
+            "reactions": {
+              "type": "object",
+              "properties": {
+                "url": {
+                  "type": "string"
+                },
+                "total_count": {
+                  "type": "integer"
+                },
+                "+1": {
+                  "type": "integer"
+                },
+                "-1": {
+                  "type": "integer"
+                },
+                "laugh": {
+                  "type": "integer"
+                },
+                "confused": {
+                  "type": "integer"
+                },
+                "heart": {
+                  "type": "integer"
+                },
+                "hooray": {
+                  "type": "integer"
+                },
+                "eyes": {
+                  "type": "integer"
+                },
+                "rocket": {
+                  "type": "integer"
+                }
+              }
             }
           }
         }

{airbyte-source-github-1.5.7 → airbyte_source_github-1.6.1}/source_github/source.py

@@ -61,6 +61,9 @@ from .utils import read_full_refresh
 
 
 class SourceGithub(AbstractSource):
+
+    continue_sync_on_stream_failure = True
+
     @staticmethod
     def _get_org_repositories(config: Mapping[str, Any], authenticator: MultipleTokenAuthenticator) -> Tuple[List[str], List[str]]:
         """

{airbyte-source-github-1.5.7 → airbyte_source_github-1.6.1}/source_github/streams.py

@@ -14,6 +14,7 @@ from airbyte_cdk.models import Type as MessageType
 from airbyte_cdk.sources.streams.availability_strategy import AvailabilityStrategy
 from airbyte_cdk.sources.streams.http import HttpStream
 from airbyte_cdk.sources.streams.http.exceptions import DefaultBackoffException
+from airbyte_cdk.utils import AirbyteTracedException
 from requests.exceptions import HTTPError
 
 from . import constants
@@ -214,10 +215,9 @@ class GithubStreamABC(HttpStream, ABC):
                 raise e
 
             self.logger.warning(error_msg)
-        except GitHubAPILimitException:
-            self.logger.warning(
-                f"Stream: `{self.name}`, slice: `{stream_slice}`. Limits for all provided tokens are reached, please try again later"
-            )
+        except GitHubAPILimitException as e:
+            message = f"Stream: `{self.name}`, slice: `{stream_slice}`. Limits for all provided tokens are reached, please try again later"
+            raise AirbyteTracedException(message) from e
 
 
 class GithubStream(GithubStreamABC):

airbyte-source-github-1.5.7/PKG-INFO

@@ -1,144 +0,0 @@
-Metadata-Version: 2.1
-Name: airbyte-source-github
-Version: 1.5.7
-Summary: Source implementation for Github.
-Author: Airbyte
-Author-email: contact@airbyte.io
-Description-Content-Type: text/markdown
-Requires-Dist: airbyte-cdk
-Requires-Dist: sgqlc
-Provides-Extra: tests
-Requires-Dist: requests-mock~=1.9.3; extra == "tests"
-Requires-Dist: pytest-mock~=3.6.1; extra == "tests"
-Requires-Dist: pytest~=6.2; extra == "tests"
-Requires-Dist: responses~=0.23.1; extra == "tests"
-Requires-Dist: freezegun~=1.2; extra == "tests"
-
-# Github Source
-
-This is the repository for the Github source connector, written in Python.
-For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.io/integrations/sources/github).
-
-
-**To iterate on this connector, make sure to complete this prerequisites section.**
-
-
-From this connector directory, create a virtual environment:
-```
-python -m venv .venv
-```
-
-This will generate a virtualenv for this module in `.venv/`. Make sure this venv is active in your
-development environment of choice. To activate it from the terminal, run:
-```
-source .venv/bin/activate
-pip install -r requirements.txt
-pip install '.[tests]'
-```
-If you are in an IDE, follow your IDE's instructions to activate the virtualenv.
-
-Note that while we are installing dependencies from `requirements.txt`, you should only edit `setup.py` for your dependencies. `requirements.txt` is
-used for editable installs (`pip install -e`) to pull in Python dependencies from the monorepo and will call `setup.py`.
-If this is mumbo jumbo to you, don't worry about it, just put your deps in `setup.py` but install using `pip install -r requirements.txt` and everything
-should work as you expect.
-
-**If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.io/integrations/sources/github)
-to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_github/spec.json` file.
-Note that any directory named `secrets` is gitignored across the entire Airbyte repo, so there is no danger of accidentally checking in sensitive information.
-See `integration_tests/sample_config.json` for a sample config file.
-
-**If you are an Airbyte core member**, copy the credentials in Lastpass under the secret name `source github test creds`
-and place them into `secrets/config.json`.
-
-```
-python main.py spec
-python main.py check --config secrets/config.json
-python main.py discover --config secrets/config.json
-python main.py read --config secrets/config.json --catalog integration_tests/configured_catalog.json
-```
-
-
-
-
-The Airbyte way of building this connector is to use our `airbyte-ci` tool.
-You can follow install instructions [here](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md#L1).
-Then running the following command will build your connector:
-
-```bash
-airbyte-ci connectors --name=source-github build
-```
-Once the command is done, you will find your connector image in your local docker registry: `airbyte/source-github:dev`.
-
-When contributing on our connector you might need to customize the build process to add a system dependency or set an env var.
-You can customize our build process by adding a `build_customization.py` module to your connector.
-This module should contain a `pre_connector_install` and `post_connector_install` async function that will mutate the base image and the connector container respectively.
-It will be imported at runtime by our build process and the functions will be called if they exist.
-
-Here is an example of a `build_customization.py` module:
-```python
-from __future__ import annotations
-
-from typing import TYPE_CHECKING
-
-if TYPE_CHECKING:
-from dagger import Container
-
-
-async def pre_connector_install(base_image_container: Container) -> Container:
-return await base_image_container.with_env_variable("MY_PRE_BUILD_ENV_VAR", "my_pre_build_env_var_value")
-
-async def post_connector_install(connector_container: Container) -> Container:
-return await connector_container.with_env_variable("MY_POST_BUILD_ENV_VAR", "my_post_build_env_var_value")
-```
-
-This connector is built using our dynamic built process in `airbyte-ci`.
-The base image used to build it is defined within the metadata.yaml file under the `connectorBuildOptions`.
-The build logic is defined using [Dagger](https://dagger.io/) [here](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/pipelines/builds/python_connectors.py).
-It does not rely on a Dockerfile.
-
-If you would like to patch our connector and build your own a simple approach would be to:
-
-1. Create your own Dockerfile based on the latest version of the connector image.
-```Dockerfile
-FROM airbyte/source-github:latest
-
-COPY . ./airbyte/integration_code
-RUN pip install ./airbyte/integration_code
-
-```
-Please use this as an example. This is not optimized.
-
-2. Build your image:
-```bash
-docker build -t airbyte/source-github:dev .
-docker run airbyte/source-github:dev spec
-```
-Then run any of the connector commands as follows:
-```
-docker run --rm airbyte/source-github:dev spec
-docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-github:dev check --config /secrets/config.json
-docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-github:dev discover --config /secrets/config.json
-docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-github:dev read --config /secrets/config.json --catalog /integration_tests/configured_catalog.json
-```
-
-You can run our full test suite locally using [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md):
-```bash
-airbyte-ci connectors --name=source-github test
-```
-
-Customize `acceptance-test-config.yml` file to configure tests. See [Connector Acceptance Tests](https://docs.airbyte.com/connector-development/testing-connectors/connector-acceptance-tests-reference) for more information.
-If your connector requires to create or destroy resources for use during acceptance tests create fixtures for it and place them inside integration_tests/acceptance.py.
-
-All of your dependencies should go in `setup.py`, NOT `requirements.txt`. The requirements file is only used to connect internal Airbyte dependencies in the monorepo for local development.
-We split dependencies between two groups, dependencies that are:
-* required for your connector to work need to go to `MAIN_REQUIREMENTS` list.
-* required for the testing need to go to `TEST_REQUIREMENTS` list
-
-You've checked out the repo, implemented a million dollar feature, and you're ready to share your changes with the world. Now what?
-1. Make sure your changes are passing our test suite: `airbyte-ci connectors --name=source-github test`
-2. Bump the connector version in `metadata.yaml`: increment the `dockerImageTag` value. Please follow [semantic versioning for connectors](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#semantic-versioning-for-connectors).
-3. Make sure the `metadata.yaml` content is up to date.
-4. Make the connector documentation and its changelog is up to date (`docs/integrations/sources/github.md`).
-5. Create a Pull Request: use [our PR naming conventions](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#pull-request-title-convention).
-6. Pat yourself on the back for being an awesome contributor.
-7. Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.