# Add files from remote repos to custom models > Add files from remote repos to custom models - Add files from remote repositories, including > Bitbucket, GitHub, GitHub Enterprise, S3, GitLab, and GitLab Enterprise to the models you create in > the Custom Model Workshop. This Markdown file sits beside the HTML page at the same path (with a `.md` suffix). It summarizes the topic and lists links for tools and LLM context. Companion generated at `2026-04-24T16:03:56.557451+00:00` (UTC). ## Primary page - [Add files from remote repos to custom models](https://docs.datarobot.com/en/docs/classic-ui/mlops/deployment/custom-models/custom-model-workshop/custom-model-repos.html): Full documentation for this topic (HTML). ## Sections on this page - [Add a remote repository](https://docs.datarobot.com/en/docs/classic-ui/mlops/deployment/custom-models/custom-model-workshop/custom-model-repos.html#add-a-remote-repository): In-page section heading. - [Bitbucket Server repository](https://docs.datarobot.com/en/docs/classic-ui/mlops/deployment/custom-models/custom-model-workshop/custom-model-repos.html#bitbucket-server-repository): In-page section heading. - [GitHub repository](https://docs.datarobot.com/en/docs/classic-ui/mlops/deployment/custom-models/custom-model-workshop/custom-model-repos.html#github-repository): In-page section heading. - [GitHub organization repository access](https://docs.datarobot.com/en/docs/classic-ui/mlops/deployment/custom-models/custom-model-workshop/custom-model-repos.html#github-organization-repository-access): In-page section heading. - [GitHub Enterprise repository](https://docs.datarobot.com/en/docs/classic-ui/mlops/deployment/custom-models/custom-model-workshop/custom-model-repos.html#github-enterprise-repository): In-page section heading. - [Git Large File Storage](https://docs.datarobot.com/en/docs/classic-ui/mlops/deployment/custom-models/custom-model-workshop/custom-model-repos.html#git-large-file-storage): In-page section heading. - [S3 repository](https://docs.datarobot.com/en/docs/classic-ui/mlops/deployment/custom-models/custom-model-workshop/custom-model-repos.html#s3-repository): In-page section heading. - [AWS S3 access configuration](https://docs.datarobot.com/en/docs/classic-ui/mlops/deployment/custom-models/custom-model-workshop/custom-model-repos.html#aws-s3-access-configuration): In-page section heading. - [GitLab Cloud repository](https://docs.datarobot.com/en/docs/classic-ui/mlops/deployment/custom-models/custom-model-workshop/custom-model-repos.html#gitlab-cloud-repository): In-page section heading. - [GitLab Enterprise repository](https://docs.datarobot.com/en/docs/classic-ui/mlops/deployment/custom-models/custom-model-workshop/custom-model-repos.html#gitlab-enterprise-repository): In-page section heading. - [Create a personal access token for GitLab Enterprise](https://docs.datarobot.com/en/docs/classic-ui/mlops/deployment/custom-models/custom-model-workshop/custom-model-repos.html#create-a-personal-access-token-for-GitLab-enterprise): In-page section heading. - [Pull files from the repository](https://docs.datarobot.com/en/docs/classic-ui/mlops/deployment/custom-models/custom-model-workshop/custom-model-repos.html#pull-files-from-the-repository): In-page section heading. ## Related documentation - [Classic UI documentation](https://docs.datarobot.com/en/docs/classic-ui/index.html): Linked from this page. - [MLOps](https://docs.datarobot.com/en/docs/classic-ui/mlops/index.html): Linked from this page. - [Deployment](https://docs.datarobot.com/en/docs/classic-ui/mlops/deployment/index.html): Linked from this page. - [Prepare custom models for deployment](https://docs.datarobot.com/en/docs/classic-ui/mlops/deployment/custom-models/index.html): Linked from this page. - [Custom Model Workshop](https://docs.datarobot.com/en/docs/classic-ui/mlops/deployment/custom-models/custom-model-workshop/index.html): Linked from this page. - [add a model](https://docs.datarobot.com/en/docs/classic-ui/mlops/deployment/custom-models/custom-model-workshop/custom-inf-model.html#create-a-new-custom-model): Linked from this page. ## Documentation content # Add files from remote repos to custom models If you [add a model](https://docs.datarobot.com/en/docs/classic-ui/mlops/deployment/custom-models/custom-model-workshop/custom-inf-model.html#create-a-new-custom-model) to the Custom Model Workshop, you can add files to that model from a wide range of repositories, including Bitbucket, GitHub, GitHub Enterprise, S3, GitLab, and GitLab Enterprise. After adding a repository to DataRobot, you can [pull files](https://docs.datarobot.com/en/docs/classic-ui/mlops/deployment/custom-models/custom-model-workshop/custom-model-repos.html#pull-files-from-the-repository) from the repository and include them in the custom model. ## Add a remote repository The following steps show how to add a remote repository so that you can pull files into a custom model: **From the Remote Repositories page:** On any page, click your profile avatar (or the default avatar ) in the upper-right corner of DataRobot, then click Remote repositories . On the Remote Repositories page, click Add repository , and then select a repository provider to integrate a new remote repository with DataRobot. **From the Assemble tab:** On the Model Registry > Custom Model Workshop tab, select a custom model you wish to add files to and navigate to the Assemble tab. On the Assemble tab, click Select remote repository . Click Add repository , and then select a repository provider to integrate a new remote repository with DataRobot. After you select the type of repository to register, follow the relevant process from the list below: - Bitbucket Server - GitHub - GitHub Enterprise - S3 - GitLab - GitLab Enterprise ### Bitbucket Server repository To register a Bitbucket Server repository, in the Add Bitbucket Server repository modal, configure the required fields: | Field | Description | | --- | --- | | Name | The name of the Bitbucket Server repository. | | Repository location | The URL for the Bitbucket Server repository that appears in the browser address bar when accessed. Alternatively, select Clone from the Bitbucket Server UI and paste the URL. | | Personal access token | The token used to grant DataRobot access to the Bitbucket Server repository. Generate this token from the Bitbucket Server UI. | | Description | (Optional) A description of the Bitbucket Server repository. | After you configure the required fields, click Test to verify connection to the repository. Once you verify the connection, click Add repository. ### GitHub repository To add a GitHub repository, in the Add GitHub repository modal, the steps for connecting to the repository depend on the connection method. **GitHub application:** The primary method for adding a GitHub repository is to authorize the DataRobot User Models Integration application for GitHub. Click Authorize GitHub app, then, configure the following fields: [https://docs.datarobot.com/en/docs/images/custom-repo-4.png](https://docs.datarobot.com/en/docs/images/custom-repo-4.png) Field Description Name The name of the GitHub repository. Repository Enter the GitHub repository URL. Start typing the repository name and repositories will populate in the autocomplete dropdown. To use a private repository, grant the GitHub app access to private repositories. When you grant access to a private repository , its URL is added to the Repository autocomplete dropdown. To use an external public GitHub repository, you must obtain the URL from the repo . Description (Optional) A description of the GitHub repository. Private repository permissions To use a private repository , click Edit repository permissions in the Add GitHub repository window. This gives the GitHub app access to your private repositories. You can give access to all current and future private repositories or a selected list of repositories External GitHub repositories To use an external public GitHub repository that is not owned by you or your organization, navigate to the repository in GitHub and click Code . Copy and paste the URL into the Repository field of the Add GitHub repository window. After access is granted, the private repositories appear in the autocomplete dropdown for the Repository field. **Personal access token:** The fallback method for adding a GitHub repository is to provide a repository location and personal access token. [https://docs.datarobot.com/en/docs/images/add-github-repo-classic.png](https://docs.datarobot.com/en/docs/images/add-github-repo-classic.png) Field Description Name The name of the GitHub repository. Repository location The URL for the GitHub repository that appears in the browser address bar when accessed. Alternatively, select Clone from the GitHub UI and paste the URL. Personal access token (Optional) The token used to grant DataRobot access to the GitHub repository. Generate this token from the GitHub UI. A token isn`t required for public repositories. Description (Optional) A description of the GitHub repository. After you configure the required fields, click Test to verify connection to the repository. Once you verify the connection, click Add repository. > [!TIP] GitHub repository organizations > You can add repositories from any [GitHub organization](https://docs.datarobot.com/en/docs/classic-ui/mlops/deployment/custom-models/custom-model-workshop/custom-model-repos.html#github-organization-repository-access) you belong to. #### GitHub organization repository access If you belong to a GitHub organization, you can request access to an organization's repository for use with DataRobot. A request for access notifies the GitHub admin, who then who approves or denies your access request. > [!NOTE] Organization repository access > If your admin approves a single user's access request, access is provided to all DataRobot users in that user's organization without any additional configuration. For more information, reference the [GitHub documentation](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories). ### GitHub Enterprise repository To register a GitHub Enterprise repository, in the Add GitHub Enterprise repository modal, configure the required fields: | Field | Description | | --- | --- | | Name | The name of the GitHub Enterprise repository. | | Repository location | The URL for the GitHub Enterprise repository that appears in the browser address bar when accessed. Alternatively, select Clone from the GitHub Enterprise UI and paste the URL. | | Personal access token | The token used to grant DataRobot access to the GitHub Enterprise repository. Generate this token from the GitHub UI. | | Description | (Optional) A description of the GitHub Enterprise repository. | After you configure the required fields, click Test to verify connection to the repository. Once you verify the connection, click Add repository. #### Git Large File Storage Git Large File Storage (LFS) is supported by default for GitHub integrations. Reference the [Git documentation](https://git-lfs.github.com) to learn more. Git LFS support for GitHub always requires having the GitHub application installed on the target repository, even if it's a public repository. Any non-authorized requests to the LFS API will fail with an HTTP 403. ### S3 repository To register an S3 repository, in the Add S3 repository modal, configure the required fields. | Field | Description | | --- | --- | | Name | The name of the S3 repository. | | Bucket name | The name of the S3 bucket. If you are adding a public S3 repository, this is the only field you must complete. | | Access key ID | The key used to sign programmatic requests made to AWS. Use with the AWS Secret Access Key to authenticate requests to pull from the S3 repository. Required for private S3 repositories. | | Secret access key | The key used to sign programmatic requests made to AWS. Use with the AWS Access Key ID to authenticate requests to pull from the S3 repository. Required for private S3 repositories. | | Session token | (Optional) A token that validates temporary security credentials when making a call to an S3 bucket. | | Description | (Optional) A description of the S3 repository. | After you configure the required fields, click Test to verify connection to the repository. Once you verify the connection, click Add repository. > [!NOTE] S3 credentials > AWS credentials are optional for public buckets. You can remove any S3 credentials by editing the repository connection. Select the connection and click Clear credentials. #### AWS S3 access configuration DataRobot requires the AWS S3 `ListBucket` and `GetObject` permissions in order to ingest data. These permissions should be applied as an additional AWS IAM Policy for the AWS user or role the cluster uses for access. For example, to allow ingestion of data from a private bucket named `examplebucket`, apply the following policy: ``` { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": ["s3:ListBucket"], "Resource": ["arn:aws:s3:::examplebucket"] }, { "Effect": "Allow", "Action": ["s3:GetObject"], "Resource": ["arn:aws:s3:::examplebucket/*"] } ] } ``` ### GitLab Cloud repository To add a GitLab repository, in the Add GitLab repository modal, the steps for connecting to the repository depend on the connection method. **GitLab application:** The primary method for adding a GitLab repository is to authorize the DataRobot User Models Integration application for GitLab. [https://docs.datarobot.com/en/docs/images/gitlab-1.png](https://docs.datarobot.com/en/docs/images/gitlab-1.png) Click Authorize GitLab app, grant access, and configure the following fields: [https://docs.datarobot.com/en/docs/images/gitlab-2.png](https://docs.datarobot.com/en/docs/images/gitlab-2.png) Field Description Name The name of the GitLab repository. Repository Enter the GitLab repository URL. Start typing the repository name and repositories will populate in the autocomplete dropdown. Description (Optional) A description of the GitLab repository. **Personal access token:** The fallback method for adding a GitLab repository is to provide a repository location and personal access token. [https://docs.datarobot.com/en/docs/images/add-gitlab-repo-classic.png](https://docs.datarobot.com/en/docs/images/add-gitlab-repo-classic.png) Field Description Name The name of the GitLab repository. Repository location The URL for the GitLab repository that appears in the browser address bar when accessed. Personal access token (Optional) Enter the token used to grant DataRobot access to the GitLab repository. Generate this token from GitLab. A token isn`t required for public repositories. Description (Optional) A description of the GitLab repository. After you configure the required fields, click Test to verify connection to the repository. Once you verify the connection, click Add repository. ### GitLab Enterprise repository To register a GitLab Enterprise repository, in the Add GitLab Enterprise repository modal, configure the required fields: | Field | Description | | --- | --- | | Name | The name of the GitLab Enterprise repository. | | Repository location | The URL for the GitLab Enterprise repository that appears in the browser address bar when accessed. | | Personal access token | (Optional) Enter the token used to grant DataRobot access to the GitLab Enterprise repository. Generate this token from GitLab Enterprise. A token isn`t required for public repositories. | | Description | (Optional) A description of the GitLab Enterprise repository. | After you configure the required fields, click Test to verify connection to the repository. Once you verify the connection, click Add repository. #### Create a personal access token for GitLab Enterprise To create a personal access token: 1. Navigate to GitLab. 2. Enter a name for the new token, set the mandatory scopes (read_apiandread_repository), and clickCreate personal access token. The newly generated token appears at the top of the page. 3. Enter the new token into thePersonal access tokenfield in theAdd GitLab Enterprise repositorywindow. ## Pull files from the repository After you add a repository to DataRobot, you can pull files from the repository and include them in the custom model. To pull files from a repository: 1. In the top navigation bar, clickModel Registry. 2. ClickCustom Model Workshop, click theModelstab, and select a model from the list. 3. UnderAssemble Model, clickSelect remote repository. Select a base environmentIf theModelgroup box is empty, select aBase Environmentfor the model. 4. In theSelect a remote repositorydialog box, select a repository in the list and clickSelect content. 5. In thePull from GitHub repositorydialog box, select the checkbox for any files or folders you want to pull into the custom model. You can also clickSelect allto select every file in the repository, or, after selecting one or more files, clickDeselect allto clear your selections. Repository typeThis step uses GitHub as an example; however, the process is the same for each repository type. TipYou can see how many files you have selected at the bottom of the dialog box (e.g.,+ 4 files will be added). 6. Once you select the files you want to pull into the custom model, clickPull. The added files appear under theModelheader as part of the custom model.