From 8a771907a0b954fd356cd5bb11853158abca8242 Mon Sep 17 00:00:00 2001 From: Tim McFadden <52185+tim775@users.noreply.github.com> Date: Thu, 10 Mar 2022 07:01:49 -0500 Subject: [PATCH] Add more context as to why the workflow scope is required. Co-authored-by: Johan Haals Signed-off-by: tim775 <52185+tim775@users.noreply.github.com> --- docs/getting-started/configuration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/getting-started/configuration.md b/docs/getting-started/configuration.md index 414ebe613a..2aa8970d52 100644 --- a/docs/getting-started/configuration.md +++ b/docs/getting-started/configuration.md @@ -218,7 +218,7 @@ for 7 days, it's a lucky number. Screenshot of the GitHub Personal Access Token creation page

-Set the scope to your likings. For this tutorial, selecting "repo" and "workflow" should be +Set the scope to your likings. For this tutorial, selecting "repo" and "workflow" is required as the scaffolding job in this guide configures a GitHub actions workflow for the newly created project. enough. In the `app-config.yaml`, search for `integrations:` and add your token, like we