Skip to main content
GitHub list repository collaborators action lists collaborators for a specific GitHub repository. This is a read-only action that returns users with direct access permissions, which is useful for auditing repository access or using the collaborator list in multi-step workflows.

​
Prerequisites

  • Your admin must install and configure the GitHub connector, add the GitHub actions pack under Admin > Actions, and enable this action.
  • A GitHub app must be installed on the relevant organization(s) and linked to the correct GitHub datasource in the Glean admin console.

​
Supported parameters

ParameterTypeDescription
OwnerStringThe username of the account that owns the repository (case-insensitive).
RepositoryStringThe name of the repository without the .git extension (case-insensitive).
AffiliationStringFilter by affiliation: outside (non-org members), direct (direct permissions), or all (all visible collaborators).
PageIntegerThe page number of results to retrieve for pagination.
Results per pageIntegerNumber of results per page (maximum 100).
Permission levelStringFilter collaborators by their repository permission level.

​
Usage examples

  • “List all collaborators for the ‘facebook/react’ repository and show their permission levels.”
  • “Who has write access to the ‘microsoft/vscode’ repository?”
  • “Show me all outside collaborators for the ‘tensorflow/tensorflow’ repository.”

​
Troubleshooting

  • Possible cause: The GitHub connector is not fully set up, the GitHub app is not installed on the target organization, or the app is missing required permissions.
  • Fix: Confirm that the GitHub connector is installed and authenticated, that the GitHub app is installed on the correct organization(s), and that it has the necessary repository scopes. If using a custom app, verify that permissions to read repository collaborators are enabled.
  • Possible cause: The owner or repository name is incorrect, the repository does not exist, or the authenticated user does not have access to it.
  • Fix: Verify that the repository exists at https://github.com/owner/repo and that the authenticated user has at least read access to it. Check for typos in the owner or repository name.
  • Possible cause: The repository may have no collaborators, the affiliation filter is too restrictive, or the authenticated user can only see a subset of collaborators.
  • Fix: Try using affiliation: all to see all visible collaborators. Verify that the authenticated user has sufficient permissions to view the collaborator list. Note that only repository admins can see all collaborators.
  • Possible cause: The GitHub organization has restricted third-party OAuth apps, so the app used by this action is not allowed to access repository collaborators.
  • Fix: Ask your GitHub organization admin to enable the app or adjust OAuth App access restrictions for the relevant repositories.

​
FAQs

It returns users with direct access permissions to the specified GitHub repository. You can filter the list using the Affiliation parameter (outside, direct, or all) and further filter by Permission level when needed.
Collaborators can have the following permission levels: read (pull), triage (triage issues/PRs), write (push), maintain (manage without destructive actions), or admin (full access). The specific levels available depend on your repository settings.
Yes, as long as the authenticated user has access to the private repository. The action respects GitHub’s access control and only returns collaborators for repositories the user can access.
  • outside: Collaborators who are not members of the organization (for organization-owned repos)
  • direct: Collaborators with direct permissions to the repository
  • all: All collaborators visible to the authenticated user (default)