GitHub Repository Access
Use these actions to grant repository access after a mold creates or updates a repository.
github.team.add
Section titled “github.team.add”Adds a GitHub team to a repository, or updates its permission if the team already has access.
steps: - id: add-team name: Grant team access action: github.team.add inputs: owner: "${{ inputs.owner }}" repo: "${{ inputs.name }}" catalog_team: "${{ inputs.team }}" permission: pushInputs:
| Input | Required | Description |
|---|---|---|
owner | Yes | Repository owner or organization |
repo | Yes | Repository name |
team_slug | Either team_slug or catalog_team | GitHub team slug |
catalog_team | Either team_slug or catalog_team | Shoehorn catalog team selection |
permission | No | GitHub permission, default push |
Use catalog_team when the mold form uses catalog:teams. Forge resolves the catalog team to the GitHub team slug when a mapping is available.
inputs: type: object required: - team properties: team: type: string title: Owning team ui:options: source: catalog:teams placeholder: Select a teamgithub.collaborator.add
Section titled “github.collaborator.add”Adds an individual collaborator to a repository, or updates their permission if they already have access.
steps: - id: add-collaborator name: Grant user access action: github.collaborator.add inputs: owner: "${{ inputs.owner }}" repo: "${{ inputs.name }}" username: "${{ inputs.githubUsername }}" permission: pushInputs:
| Input | Required | Description |
|---|---|---|
owner | Yes | Repository owner or organization |
repo | Yes | Repository name |
username | Yes | GitHub username |
permission | No | GitHub permission, default push |