From a48cb2b0bfc0606160f33d4b53c1e0ffc863c064 Mon Sep 17 00:00:00 2001 From: Evgeny Lupanov Date: Thu, 14 May 2020 18:53:22 +0300 Subject: [PATCH] fix: actions readme formatting --- .github/workflows/ACTION_TRIGGER_GUIDE.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/.github/workflows/ACTION_TRIGGER_GUIDE.md b/.github/workflows/ACTION_TRIGGER_GUIDE.md index a9820da5..c0bf75cf 100644 --- a/.github/workflows/ACTION_TRIGGER_GUIDE.md +++ b/.github/workflows/ACTION_TRIGGER_GUIDE.md @@ -2,11 +2,11 @@ In order to trigger `deploy-to-demo` action you should execute the following curl: -`curl -H "Accept: application/vnd.github.everest-preview+json" \ --H "Authorization: token " \ ---request POST \ ---data '{"event_type": "deploy-to-demo"}' \ -https://api.github.com/repos/akveo/ngx-admin/dispatches` +`curl -H "Accept: application/vnd.github.everest-preview+json" \` +`-H "Authorization: token " \` +`--request POST \` +`--data '{"event_type": "deploy-to-demo"}' \` +`https://api.github.com/repos/akveo/ngx-admin/dispatches` This curl expects `ACCESS_TOKEN` input parameter
`ACCESS_TOKEN`: A personal access token. Creating a [personal access token guide](https://help.github.com/en/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)