GitHub

This page was recently updated. What do you think about it? Let us know!.

Connect GitHub to your preprocessing pipeline, and use the Unstructured Ingest CLI or the Unstructured Ingest Python library to batch process all your documents and store structured outputs locally on your filesystem.

The requirements are as follows.

• The user or organization name, and the repository name, for the target GitHub repository, for example Unstructured-IO/docs.
• The name of a branch to access in the repository. By default, the repository’s default branch is used.
• A GitHub account.
• A GitHub personal access token for the account.
• If you are accessing a private GitHub repository, the repository must grant the appropriate access permissions to the GitHub account.

The GitHub connector dependencies:

CLI, Python

pip install "unstructured-ingest[github]"

You might also need to install additional dependencies, depending on your needs. Learn more.

The following environment variables:

• GITHUB_URL - The user or organization name, and the repository name, for the target GitHub repository; for example Unstructured-IO/docs, represented by --url (CLI) or url (Python).
• GITHUB_BRANCH - The name of the target branch in the repository, for example main, represented by --branch (CLI) or branch (Python). By default, the repository’s default branch is used.
• GITHUB_ACCESS_TOKEN - The value of your GitHub access token, represented by --access-token (CLI) or access_token (Python).

Now call the Unstructured Ingest CLI or the Unstructured Ingest Python library. The destination connector can be any of the ones supported. This example uses the local destination connector.

This example sends data to Unstructured for processing by default. To process data locally instead, see the instructions at the end of this page.

CLI

#!/usr/bin/env bash

# Chunking and embedding are optional.

unstructured-ingest \
  github \
    --access-token $GITHUB_ACCESS_TOKEN \
    --url $GITHUB_URL \
    --branch $GITHUB_BRANCH \
    --recursive \
    --output-dir $LOCAL_FILE_OUTPUT_DIR \
    --partition-by-api \
    --api-key $UNSTRUCTURED_API_KEY \
    --partition-endpoint $UNSTRUCTURED_API_URL \
    --strategy hi_res \
    --additional-partition-args="{\"split_pdf_page\":\"true\", \"split_pdf_allow_failed\":\"true\", \"split_pdf_concurrency_level\": 15}"

For the Unstructured Ingest CLI and the Unstructured Ingest Python library, you can use the --partition-by-api option (CLI) or partition_by_api (Python) parameter to specify where files are processed:

• To do local file processing, omit --partition-by-api (CLI) or partition_by_api (Python), or explicitly specify partition_by_api=False (Python).

  Local file processing does not use an Unstructured API key or API URL, so you can also omit the following, if they appear:

  • --api-key $UNSTRUCTURED_API_KEY (CLI) or api_key=os.getenv("UNSTRUCTURED_API_KEY") (Python)
  • --partition-endpoint $UNSTRUCTURED_API_URL (CLI) or partition_endpoint=os.getenv("UNSTRUCTURED_API_URL") (Python)
  • The environment variables UNSTRUCTURED_API_KEY and UNSTRUCTURED_API_URL

• To send files to the Unstructured Partition Endpoint for processing, specify --partition-by-api (CLI) or partition_by_api=True (Python).

  Unstructured also requires an Unstructured API key and API URL, by adding the following:

  • --api-key $UNSTRUCTURED_API_KEY (CLI) or api_key=os.getenv("UNSTRUCTURED_API_KEY") (Python)
  • --partition-endpoint $UNSTRUCTURED_API_URL (CLI) or partition_endpoint=os.getenv("UNSTRUCTURED_API_URL") (Python)
  • The environment variables UNSTRUCTURED_API_KEY and UNSTRUCTURED_API_URL, representing your API key and API URL, respectively.
  You must specify the API URL only if you are not using the default API URL for Unstructured Ingest, for example, if you are using a self-hosted instance of the Unstructured API.

  The default API URL for Unstructured Ingest is https://api.unstructuredapp.io/general/v0/general, which is the API URL for the Unstructured Partition Endpoint.

  If you do not have an API key, get one now.

  If the Unstructured API is self-hosted, the process for generating Unstructured API keys, and the Unstructured API URL that you use, are different. For details, contact Unstructured Sales at [e-mail].