The Adaptavist Group LogoDocumentation

Importing Repos

Managing owners now have a better way to import repositories into Venue.sh—either one repo at a time or many at once—in a simple, user-friendly process. Gone are the days of creating yaml files from scratch and adding details to the catalog via template. Now you can import and manage as many repos as you like in a matter of minutes, all without writing a single line of code.

Importing repos is part of the onboarding process for Venue owners. The four onboarding steps appear on the Home screen until each step is completed.

To reiterate, the four onboarding steps for owners are as follows:

  1. Create a connection
  2. Create a team
  3. Enable plugins
  4. Import repositories
Note:

The Get started with Venue.sh onboarding will disappear from the Home screen once all four onboarding steps are complete.

Importing Repos into Venue.sh

Begin the import process from your Venue Home screen.

Note: Prerequisites

Ensure onboarding Steps 1-3 (outlined above) are complete before your import repos.

  1. Click one of the following options, each of which leads to the same import process
    • Run an import from the Quick Start tile
    • Step 4: Import repositories from the onboarding steps
    • Imports from the left-side navigation
    The New Import wizard appears.
  2. Select the Git connection from which you want to pull a list of repos, then click Next step.

    A list of available repos is generated on the screen.

  3. Select the repos you want to import into the venue, then click Next step.

    The configuration screen appears.

  4. Select your metadata preferences for each repo from the drop-down options, and type your desired values into the free-text fields, e.g., Namespace, Tags, and Audience.
    Note:
    • Adding metadata details to new entities helps track entities within the Venue catalog.
    • Tags accepts one or more values per repository. Type a tag and press Enter to add another. Use Apply to all to copy tags (and other column values) to every row when you import many repositories at once.
    • Audience controls who can see the entity after import. The default is Organization. See Catalog visibility (audience) below.
  5. Optional: If active, click Configure optional fields to select and add fields from your enabled plugins to the configuration table. If no plugins are enabled, this button will be inactive.
  6. Click Next step.

    The Finalize import summary appears.

  7. Review the values and, once approved, click Import.
    The import runs, and a success message appears.
  8. Click Go to Catalog to view and/or edit the new components.
    Tip:

    In the catalog, filter results using the options on the left side of the page, or use the keyword search. Click Edit to make updates to a component or other entities within the catalog.

    You can update the title, description, and audience, add Namespace and Tag values, and more.

Catalog Visibility (Audience)

When you import or edit a catalog entity, Audience decides who can discover and open it.

ValueWho can see the entity
OrganizationAnyone in your organization with catalog read access (default).
TeamMembers of the entity's owning team, plus Venue administrators and internal support roles. Everyone else cannot find or open the entity.
Team-scoped entities still appear in search, Global search, and graph views only for people who are allowed to see them. If you open a link to an entity you cannot access, Venue.sh behaves the same as for a missing entity.
Note: Team and User catalog records do not use audience. Audience applies to components and other entity kinds you import or edit in the catalog.

See Also

  • TechDocs - Publish and browse MkDocs documentation from catalog Components.
  • AI Settings - Index imported repositories for search, general AI usage, and repository-aware Assistant answers.
  • Search and navigation - Global search across catalog entities, TechDocs, and Confluence.

Search documentation

Start typing to search the docs.