You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`GH_TOKEN`| True | "" | The GitHub Token used to scan the repository or organization. Must have write access to all repository you are interested in scanning so that an issue or pull request can be created. |
31
-
|`GH_ENTERPRISE_URL`| False | "" | The `GH_ENTERPRISE_URL` is used to connect to an enterprise server instance of GitHub. github.com users should not enter anything here. |
32
-
|`ORGANIZATION`| Required to have `ORGANIZATION` or `REPOSITORY`|| The name of the GitHub organization which you want this action to work from. ie. github.com/github would be `github`|
33
-
|`REPOSITORY`| Required to have `ORGANIZATION` or `REPOSITORY`|| The name of the repository and organization which you want this action to work from. ie. `github/cleanowners` or a comma separated list of multiple repositories `github/cleanowners,super-linter/super-linter`|
34
-
|`EXEMPT_REPOS`| False | "" | These repositories will be exempt from this action. ex: If my org is set to `github` then I might want to exempt a few of the repos but get the rest by setting `EXEMPT_REPOS` to `github/cleanowners,github/contributors`|
35
-
|`DRY_RUN`| False | false | If set to true, this action will not create any pull requests. It will only log the repositories that could have the `CODEOWNERS` file updated. This is useful for testing or discovering the scope of this issue in your organization. |
|`GH_TOKEN`| True | "" | The GitHub Token used to scan the repository or organization. Must have write access to all repository you are interested in scanning so that an issue or pull request can be created. |
31
+
|`GH_APP_ID`| False |`""`| GitHub Application ID. See [documentation](https://docs.github.com/en/apps/creating-github-apps/authenticating-with-a-github-app/about-authentication-with-a-github-app) for more details. |
32
+
|`GH_APP_INSTALLATION_ID`| False |`""`| GitHub Application Installation ID. See [documentation](https://docs.github.com/en/apps/creating-github-apps/authenticating-with-a-github-app/about-authentication-with-a-github-app) for more details. |
33
+
|`GH_APP_PRIVATE_KEY`| False |`""`| GitHub Application Private Key. See [documentation](https://docs.github.com/en/apps/creating-github-apps/authenticating-with-a-github-app/about-authentication-with-a-github-app) for more details. |
34
+
|`GH_ENTERPRISE_URL`| False | "" | The `GH_ENTERPRISE_URL` is used to connect to an enterprise server instance of GitHub. github.com users should not enter anything here. |
35
+
|`ORGANIZATION`| Required to have `ORGANIZATION` or `REPOSITORY`|| The name of the GitHub organization which you want this action to work from. ie. github.com/github would be `github`|
36
+
|`REPOSITORY`| Required to have `ORGANIZATION` or `REPOSITORY`|| The name of the repository and organization which you want this action to work from. ie. `github/cleanowners` or a comma separated list of multiple repositories `github/cleanowners,super-linter/super-linter`|
37
+
|`EXEMPT_REPOS`| False | "" | These repositories will be exempt from this action. ex: If my org is set to `github` then I might want to exempt a few of the repos but get the rest by setting `EXEMPT_REPOS` to `github/cleanowners,github/contributors`|
38
+
|`DRY_RUN`| False | False | If set to true, this action will not create any pull requests. It will only log the repositories that could have the `CODEOWNERS` file updated. This is useful for testing or discovering the scope of this issue in your organization. |
36
39
37
40
### Example workflows
38
41
@@ -90,6 +93,37 @@ jobs:
90
93
91
94
```
92
95
96
+
### Authenticating with a GitHub App and Installation
97
+
98
+
You can authenticate as a GitHub App Installation by providing additional environment variables. If `GH_TOKEN` is set alongside these GitHub App Installation variables, the `GH_TOKEN` will be ignored and not used.
0 commit comments