Git Connections

1. Why connect a repository?

Synchronizing a Git repository lets DocuWriter.ai work on your actual codebase instead of isolated files. Once connected, repo-backed workflows can pull fresh code from the branch you specify.

A connected provider is the primary option because it enables ongoing imports and provider-dependent automation. If you cannot connect a supported provider, Full Tree Documentation also offers a secondary one-time project ZIP upload. The ZIP creates a snapshot for that documentation run; it is not a Git connection and cannot detect later code changes.

A connected repository powers workflows such as:

  • Custom Prompts
  • Tree Documentation
  • Codebase Documentation
  • README Generation
  • Release Notes
  • Source-aware Platform AI Agent answers
  • Autopilot suggestions when your code changes

2. Connecting your Git provider

You have two paths. Pick the one that fits your account and repository access model.

Option A: DocuWriter Autopilot GitHub App

For GitHub Autopilot webhook delivery and PR comments, the DocuWriter Autopilot GitHub App is recommended for repositories where the app is installed.

Install it at github.com/apps/docuwriter-ai-autopilot.

This works well for organizations that block third-party OAuth apps, and it can provide better access control and rate limits for supported Autopilot flows. Some manual repository selection and generator flows may still require a GitHub OAuth connection.

Full steps are available in Setting up Autopilot.

Option B: Provider connection

  1. Open Git Connections from the top navigation bar.
  2. In the Git providers panel, choose Connect GitHub, Connect Bitbucket, Connect GitLab, or Connect Azure DevOps.
  3. Complete the provider authorization flow or token setup.
  4. Grant repository access when prompted.
  5. After the connection is active, a Revoke token button appears.

GitHub, GitLab, and Bitbucket use provider authorization. Azure DevOps supports a personal access token by default and OAuth for supported organizational accounts.

You can link more than one provider at the same time. You can also use the GitHub App and OAuth side by side.

For self-hosted GitLab, see Self-Hosted GitLab Integration Guide.

Secondary alternative: upload a project ZIP

Use this only when you cannot or do not want to authorize a supported Git provider:

  1. Open Full Tree Documentation.
  2. Keep the connected-repository option as the default, or select Can't connect a repository? Upload a ZIP instead.
  3. Drag and drop or choose a .zip archive up to 20 GB.
  4. Select Upload Project ZIP, wait for validation and import, then review the generated documentation structure.
  5. Continue with the normal Full Tree generation flow.

The same secondary option is available during immersive onboarding in the Connect code step: select Can’t connect a provider? Upload a project ZIP.

A ZIP import is a one-time snapshot. It does not enable webhooks, automatic code-change detection, Autopilot repository sync, pull-request comments, or branch-based release notes. Upload a new ZIP and run the flow again when you want documentation from a newer code snapshot.

3. Adding a provider repository

  1. Click Add Repository.
  2. Choose the repository from the dropdown.
  3. Enter the branch you want DocuWriter.ai to analyze, such as main or develop.
  4. Click Create.
  5. Wait for the repository status to show Code Imported.

4. Repository table and status badges

Column Meaning
Repository The repository identifier, such as owner/project-name.
Branch The branch you selected.
Status Current sync status, such as Synchronizing, Indexing files, Code Imported, Creating Documentation, Comparing Branches, or a provider/import error.
Delete Removes the repository from DocuWriter.ai. It does not delete or modify the remote repository.

Use the search box to filter large repository lists.

5. Using your synced repository

Once a repository shows Code Imported:

  • It becomes selectable in repo-backed generator pickers.
  • It can be linked to a Space for Autopilot doc-update suggestions.
  • The Platform AI Agent can use linked source code for source-aware documentation checks.

6. Using the Platform AI Agent with Git connections

The Platform AI Agent can explain Git connection steps, answer questions about linked repositories, and help troubleshoot common issues.

It can also use linked source code to help review whether a documentation page is accurate.

The assistant cannot complete provider authorization or upload a project ZIP for you. It can guide you to the correct Full Tree Documentation page. Complete provider authorization, repository selection, or the one-time ZIP upload in the DocuWriter.ai browser flow.

7. Automatic PR comments

When PR comments are enabled and a repository event includes a pull request number, DocuWriter.ai can post a Markdown comment on the pull request.

The comment includes:

  • A summary of the suggested documentation updates
  • Links to apply individual suggestions

GitHub supports open pull request updates. Other providers may trigger primarily on merged or fulfilled pull request events, depending on the provider event available to DocuWriter.ai.

For setup and how Autopilot picks what to suggest, see Reviewing & applying suggestions.

8. Azure DevOps notes

Azure DevOps can be connected with a personal access token, and some account types can use OAuth. Autopilot webhook setup for Azure DevOps may require manual configuration in Azure DevOps.

If an Azure DevOps repository is missing, check that you authorized the correct organization and project, and that your token has the required repository access.

9. Security and privacy

Your code is safe and protected. DocuWriter.ai does not use your code to train models.

10. Troubleshooting

Issue Resolution
Repository list is empty Check that the connected provider account has access to the repository. Refresh or reconnect the provider. For GitHub Autopilot flows, consider the GitHub App.
Status shows an error Try syncing again. If the problem persists, contact support with the repository name and branch.
Private repository is not visible Confirm that the connecting user has access to the repository in the Git provider.
Azure DevOps repository is missing Check that you authorized the correct Azure DevOps organization and project.
Self-hosted GitLab connection fails Review the self-hosted GitLab guide and confirm the instance URL and access settings.
PR comments do not appear Check that PR comments are enabled, the provider connection is active, and the repository event includes a pull request number.

Need help?

Email [email protected]. Include the provider, repository name, branch, and the step where the connection failed.