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
Copy file name to clipboardExpand all lines: README.md
+1-3Lines changed: 1 addition & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,6 @@ All feedback regarding our GitHub Actions, as a whole, should be communicated th
29
29
1. Select a best fit workflow file from the [examples below](#example-workflows).
30
30
1. Copy that example into your repository (from step 1) and into the proper directory for GitHub Actions: `.github/workflows/` directory with the file extension `.yml` (ie. `.github/workflows/evergreen.yml`)
31
31
1. Edit the values below from the sample workflow with your information:
32
-
33
32
-`ORGANIZATION`
34
33
-`TEAM_NAME`
35
34
-`REPOSITORY`
@@ -51,7 +50,6 @@ All feedback regarding our GitHub Actions, as a whole, should be communicated th
51
50
1. Also edit the value for `GH_ENTERPRISE_URL` if you are using a GitHub Server and not using github.com.
52
51
For github.com users, leave it empty.
53
52
1. Update the value of `GH_TOKEN`. Do this by creating a [GitHub API token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#creating-a-personal-access-token-classic) with the following permissions:
54
-
55
53
- If using **classic tokens**:
56
54
-`workflow`, this will set also all permissions for `repo`
57
55
- under `admin`, `read:org` and `write:org`
@@ -107,7 +105,7 @@ The needed GitHub app permissions are the following under `Repository permission
107
105
| `GH_ENTERPRISE_URL` | False | "" | The `GH_ENTERPRISE_URL` is used to connect to an enterprise server instance of GitHub, ex: `https://yourgheserver.com`.<br>github.com users should not enter anything here. |
108
106
| `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` |
109
107
| `REPOSITORY` | Required to have `ORGANIZATION` or `REPOSITORY` | | The name of the repository and organization which you want this action to work from. ie. `github/evergreen` or a comma separated list of multiple repositories `github/evergreen,super-linter/super-linter` |
110
-
|`REPOSITORY_SEARCH_QUERY`| False | "" | When set, directs the action to use the GitHub Search API to search repositories matching this query instead of enumerating all organization repositories. Example: `org:my-org is:repository archived:false created:>2025-07-01`. |
108
+
| `REPOSITORY_SEARCH_QUERY` | False | "" | When set, directs the action to use the GitHub Search API to search repositories matching this query instead of enumerating all organization repositories. Example: `org:my-org is:repository archived:false created:>2025-07-01`. |
111
109
| `EXEMPT_REPOS` | False | "" | These repositories will be exempt from this action considering them for dependabot enablement. 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/evergreen,github/contributors` |
112
110
| `TYPE` | False | pull | Type refers to the type of action you want taken if this workflow determines that dependabot could be enabled. Valid values are `pull` or `issue`. |
113
111
| `TITLE` | False | "Enable Dependabot" | The title of the issue or pull request that will be created if dependabot could be enabled. |
0 commit comments