rmacklin/Add team label
Add team labels to new pull requests
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
- Runtime
- Deprecated runtime
Inputs
| name | description | required | default |
|---|---|---|---|
| repo_token | This token will be used to authenticate to GitHub when adding labels to your pull requests. | yes | — |
| external_repo_token | If your `teams.yml` file is in a private repository and you are using `secrets.GITHUB_TOKEN` for the `repo_token`, you'll need to pass a separate token to `external_repo_token` to give the action read access to the `teams.yml` file (`secrets.GITHUB_TOKEN` won't have access). Conversely, you do not need to set `external_repo_token` if your `teams.yml` file is in a public repository OR if you have set `repo_token` using a token that has the necessary access. | no | — |
| only_add_first_matching_label | By default, this action will only add the label of the first team that it finds for a given pull request author. If you'd like to add a label for every matching team, set this input to `false`. | no | true |
| teams_configuration_repo | The repository that contains the `teams.yml` file to use in your action. The format is either owner_name/repo_name or just repo_name. In the latter case, the action assumes the owner_name is the same as the owner of the repository in which the action is running. This does not need to be set if you follow the convention of storing your `teams.yml` file in the owner's `.github` repository. | no | .github |
| teams_configuration_path | The path to the `teams.yml` file within the teams_configuration_repo. This does not need to be set if you use the conventional path of `.github/teams.yml`. | no | .github/teams.yml |
Outputs
no outputs