# Auto-importing new repositories

*This feature is supported for GitHub organizations only.*

## About this feature

With the Auto-import feature, newly added or created repositories in your GitHub organization are automatically imported into SonarQube Cloud. It means that existing repositories in GitHub created prior to enabling the Auto-import new GitHub repositories feature are excluded.

The feature is enabled by default when you import your GitHub organization, though you can choose to disable it during the import process. You can also enable or disable this feature at any time within your SonarQube Cloud organization settings.

When applicable, auto-scan is applied to the projects created through the Auto-import. See [Automatic analysis](/sonarqube-cloud/analyzing-source-code/automatic-analysis.md) for more information.

## Important notes

* As a prerequisite for the feature, **All repositories** must be selected in GitHub’s Repository Access settings for your organization. See [Importing GitHub organization](/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/importing-github-organization.md#modifying-repository-access) for more information.
* A sudden spike in new repositories might cause you to reach your organization plan limits and pause analysis. Ensure your plan grants enough private lines of code. See [Changing your subscription plan](/sonarqube-cloud/administering-sonarcloud/managing-subscription/changing-plan.md#changing-loc) for more information.
* Repositories in GitHub that were created prior to enabling the Auto-import feature are excluded from automatic import. However, you can use the bulk import option to import all existing repositories in your organization. See [Creating your project](/sonarqube-cloud/managing-your-projects/administering-your-projects/setting-up-project.md#bulk-import) for more information.

## Enabling / disabling the Auto-import of new GitHub repositories

1. Retrieve your organization. See [Retrieving your organizations](/sonarqube-cloud/getting-started/viewing-organizations.md) for more information.
2. Go to **Administration** > **Organization settings** > **Organization binding**.
3. In **Automatically import new GitHub repositories**, select or unselect the option.

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/fe0wOpmka861gXxbWQRL" alt="Select or unselect the toggle to enable or disable the auto-import feature."><figcaption></figcaption></figure>

{% hint style="info" %}
You can also enable the feature during the import of a new organization. See [Importing GitHub organization](/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/importing-github-organization.md).
{% endhint %}

## Monitoring the Auto-import of new GitHub repositories

To check for failed imports:

1. Retrieve your organization. See [Retrieving your organizations](/sonarqube-cloud/getting-started/viewing-organizations.md) for more information.
2. Go to **Administration** > **Organization settings** > **Organization binding**. Possible failed imports are indicated below the **Automatically import new GitHub repositories** section.

## Related pages

* [Importing GitHub organization](/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/importing-github-organization.md)
* [Creating your project](/sonarqube-cloud/managing-your-projects/administering-your-projects/setting-up-project.md#bulk-import)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sonarsource.com/sonarqube-cloud/administering-sonarcloud/managing-organization/manage-org-projects/auto-import-new-repos.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.