From d3f3fcbf7bafecc0328e54c38a4d02bc912d499b Mon Sep 17 00:00:00 2001 From: Rory Abraham Date: Thu, 15 Jul 2021 17:39:31 -0600 Subject: [PATCH] Undo dummy change --- .github/workflows/README.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/.github/workflows/README.md b/.github/workflows/README.md index 3b10abeb40d2..72dccd69beb3 100644 --- a/.github/workflows/README.md +++ b/.github/workflows/README.md @@ -94,5 +94,3 @@ There are several reasons why we created these "imperative workflows" or "subrou 1. It greatly simplifies the handling of race conditions, particularly when used in combination with the [`softprops/turnstyle` action](https://github.com/softprops/turnstyle). 1. It promotes code reuse. A common set of yaml steps defined in a workflow can be extracted into an imperative workflow which can be executed from other workflows in just a few lines. 1. If a workflow is defined to execute in response to the `workflow_dispatch` event, it can be manually started by an authorized actor in the GitHub UI. - -#### Dummy change