From 8ddeeff0d33d3afddbfd4949c286ac15793933b9 Mon Sep 17 00:00:00 2001 From: Marcin Nowak-Liebiediew Date: Mon, 23 Oct 2023 15:32:09 +0200 Subject: [PATCH] Update CONTRIBUTING.md --- CONTRIBUTING.md | 17 ++++++++--------- 1 file changed, 8 insertions(+), 9 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 970ba8a03..462fb63b8 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -65,15 +65,14 @@ Mergify can take care of enforcing all of this. Just add the `automerge-squash` > [!IMPORTANT] > The 5-line script shared below summarizes the what you need to do to executed the process. It is **not recommended** to actually run it this way, because the script will approve and merge the PR - something you should do manually! - -``` -gh workflow run "prepare-release.yml" -f "semverBump=major" && sleep 3 -RUN_ID=$(gh run list --workflow=prepare-release.yml --status in_progress --json databaseId --jq '.[0].databaseId') -gh run watch $RUN_ID -gh pr review $(gh pr list --json number --jq '.[0].number') --approve -gh pr merge $(gh pr list --json number --jq '.[0].number') -# ... and you're done with releasing and publishing! -``` +> ``` +> gh workflow run "prepare-release.yml" -f "semverBump=major" && sleep 3 +> RUN_ID=$(gh run list --workflow=prepare-release.yml --status in_progress --json databaseId --jq '.[0].databaseId') +> gh run watch $RUN_ID +> gh pr review $(gh pr list --json number --jq '.[0].number') --approve +> gh pr merge $(gh pr list --json number --jq '.[0].number') +> # ... and you're done with releasing and publishing! +> ``` ## Release process