Skip to content
Nappai Documentation

Repository

Repository is the GitHub component that returns the list of repositories your GitHub account has access to: your own and those you collaborate on. For each repository you get its name, owner, description, link and a few activity details.

It is useful when you want an inventory of your code projects, or when another step of the flow needs to know which repositories exist before working with their files, issues or releases.

When to use it

  • You want a regular report of your team’s repositories, their main language and when they were last updated.
  • You need to check which repositories are private and which are public.
  • You want to hand the list of repositories to an AI agent so it can choose which one to work on.
  • You want to copy the list to a spreadsheet to keep the inventory outside GitHub.

Configuration

You need a GitHub API credential with a GitHub Personal Access Token that has access to the repositories. See Credentials.

FieldWhat it does
Credential (required)The GitHub API credential used to access your account.
Operation (required)What the component does. It has a single option, List Repositories, which returns the list of repositories.
Repository LimitThe maximum number of repositories to return, up to 1000. Default: 100.

Output

The Data output returns one item per repository, with its full name (owner/repository), name, owner, description, link, whether it is private, default branch, number of stars and forks, main language, and creation and last update dates.

You can connect the result to a spreadsheet component, to an agent, or to any of the other GitHub components, which use that same full name to identify the repository. The component can also be connected to an Agent as a tool. See Tool Mode.

Example

A software agency wants a monthly list of its projects.

  1. Add Repository with the List Repositories operation and the agency’s GitHub API credential.
  2. Leave Repository Limit at 100.
  3. Connect the Data output to a spreadsheet component that writes one row per repository with its name, language and last update date.
  4. Schedule the flow to run on the first day of each month.
  • File: read and write files in a repository.
  • Issue: manage a repository’s issues.
  • Release: manage published releases.
  • Review: work with pull requests and their reviews.