---
title: "Importing and excluding repos and projects"
canonical: "https://support.appfire.com/space/FD/1802502278/Importing%20and%20excluding%20repos%20and%20projects"
format: markdown
---
> Macro (aura-html)

After creating integrations, you can choose which repos and projects to import, which to exclude, and whether to enable auto-import.

> ℹ️ When you first set up an integration, we recommend specifically importing your most critical repos, and waiting to turn on auto-import. This will speed up initial processing of data. Turn on auto-import to gather additional data once initial processing is complete. If you experience regular integration processing delays, consider turning off auto-import.

## Importing repos and projects

<span style="color: #434343">All integrations require repos and projects to be imported for Flow to show data in reports. </span>

- <span style="color: #434343">To import specific repos, go to the </span><span style="color: #434343">**Repos**</span><span style="color: #434343"> page, then to the </span><span style="color: #434343">**Available**</span><span style="color: #434343"> tab. Learn more about </span><span style="color: #434343">[managing repositories](https://appfire.atlassian.net/wiki/spaces/FD/pages/1802109221)</span><span style="color: #434343">.</span>
- <span style="color: #434343">To import specific ticket projects, go to the integration’s details page for your ticket-based integration. In the </span><span style="color: #434343">**Tickets**</span><span style="color: #434343"> tab, click the </span><span style="color: #434343">**Import**</span><span style="color: #434343"> toggle next to all projects you want to import.</span>

<span style="color: #434343">To import repos and projects programmatically, use the auto-import feature. To edit or enable an integration’s auto-import settings:</span>

1. <span style="color: #434343">Go to the integration’s details page.</span>
2. <span style="color: #434343">In the Repos tab, if you have one, click the toggle next to </span><span style="color: #434343">**Auto-import all groups**</span><span style="color: #434343">.</span>
  1. <span style="color: #434343">If you want to auto-import all repos and projects from specific groups, but not all groups, click the toggle in the </span><span style="color: #434343">**Auto-import**</span><span style="color: #434343"> column of the table in the Repos tab.</span>

<span style="color: #434343">In the Tickets tab, if you have one, click the toggle next to </span><span style="color: #434343">**Auto-import all projects**</span><span style="color: #434343">.</span>

The auto-import feature is available for any integration. However, repo exclusion rules are only available for Git-based integrations. You cannot set up exclusion rules for ticket projects, but can set up auto-import following similar steps as in this article.

> ℹ️ Toggling off auto-import for a repo group prevents future repos from that group from importing. It does not delete previously imported repos.

## Creating repo exclusion rules

Repo exclusion rules allow you to exclude specific repos or groups of repos from being auto-imported into your account.

By adding repo exclusion rules, you will:

- See more of the data you want in Flow.
- Spend less time manually managing repos.

To edit your existing repo exclusion rules or create new ones, click the Repo exclusion tab of the integration's details page.

Create rules to exclude:

- Repos by name
- Repos by regular expression
- Repos by date
- Archived repos
- Open-source repos

Creating a repo exclusion rule for an integration does not apply to that integration’s previously-imported repos. For example, if you toggle on Exclude open-source repos, Flow will exclude all future open-source repos it discovers, but repos imported prior to creating this rule will still be included. To exclude a previously imported repo, you must manually remove the repo from the repos list.

![List of repo exclusion settings for an integration.](media://30e599e5-f81f-4878-8881-af049fdc9d55)

### Exclude repos by name

Exclude any imported or available repo by name. If the repo you wish to exclude is already imported, it will be deleted.

To exclude a repo by name:

1. Click **Add more** to locate repos by name.
2. Type in the name of the repo you would like to exclude. If the repo is already imported, it will be labeled as imported.
3. Once you have selected the repo you would like to exclude, you will be prompted to confirm your action. Click **Yes**.

Once you've confirmed your choice, the repo will no longer be imported when the auto-import feature is turned on for this integration.

### Exclude repos by regular expression

To exclude one or multiple repos by regular expression:

1. Click **Add Rule**.
2. Enter the regular expression you want to use to exclude repos.
3. Choose to match the regular expression rule on repo name or group name.
4. Optionally apply the regular expression rule to a specific group within your integration.
5. Click **Save**. You will be prompted to confirm your action.
6. Click **Yes**.

Any repo that matches this regular expression will not be imported when the auto-import feature is turned on for this integration.

### Exclude repos by date

To exclude repos by date:

1. Click **Add Date.**
2. Select a specific date from the calendar to exclude repos older or younger than the date.
3. Optionally apply the date exclusion rule to a specific group within your integration.
4. Click **Save**.
5. Click **Yes** to proceed.

### Exclude archived repos

Toggle on **Exclude archived repos** to prevent all archived repos of the selected integration from being imported.

> ℹ️ This exclusion rule applies only to GitHub and GitLab integrations.

### Exclude open-source repos

Toggle on **Exclude open-source repos** to exclude all open-source repos of the selected integration from importing.