From e0c831d748b2c62d111c19365c642cd103163e26 Mon Sep 17 00:00:00 2001 From: Rory Abraham Date: Thu, 15 Jul 2021 17:22:03 -0600 Subject: [PATCH] Make a dummy change for a test PR --- .github/workflows/README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.github/workflows/README.md b/.github/workflows/README.md index 72dccd69beb3..3b10abeb40d2 100644 --- a/.github/workflows/README.md +++ b/.github/workflows/README.md @@ -94,3 +94,5 @@ 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