From fbc72fd2befda6818105a916bbdd67fc54e3e987 Mon Sep 17 00:00:00 2001 From: William Martin Date: Mon, 14 Oct 2024 13:01:13 +0200 Subject: [PATCH] Suggest using legacy PAT for acceptance tests --- acceptance/README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/acceptance/README.md b/acceptance/README.md index 07e51f688..cc3af0f98 100644 --- a/acceptance/README.md +++ b/acceptance/README.md @@ -22,6 +22,8 @@ The organization in which the acceptance tests can manage resources in. Consider The token to use for authenticatin with the `GH_HOST`. This must already have the necessary scopes for each test, and must have permissions to act in the `GH_ACCEPTANCE_ORG`. See [Effective Test Authoring](#effective-test-authoring) for how tests must handle tokens without sufficient scopes. +It's recommended to create and use a Legacy PAT for this; Fine-Grained PATs do not offer all the necessary privileges required. You can use an OAuth token provided via `gh auth login --web` and can provide it to the acceptance tests via `GH_ACCEPTANCE_TOKEN=$(gh auth token --hostname )` but this can be a bit confusing and annoying if you `gh auth login` again without `-s` and lose the required scopes. + --- A full example invocation can be found below: