From 6dfc5e51b975e6560cd7d5a5a1608e084940aabb Mon Sep 17 00:00:00 2001 From: Tangled Date: Wed, 1 Oct 2025 13:53:21 +0000 Subject: [PATCH] docs/spindle: fix grammar Signed-off-by: Tangled --- docs/spindle/pipeline.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/spindle/pipeline.md b/docs/spindle/pipeline.md index d57f253c..ee87062d 100644 --- a/docs/spindle/pipeline.md +++ b/docs/spindle/pipeline.md @@ -21,7 +21,7 @@ The first thing to add to a workflow is the trigger, which defines when a workfl - `manual`: The workflow can be triggered manually. - `branch`: This is a **required** field that defines which branches the workflow should run for. If used with the `push` event, commits to the branch(es) listed here will trigger the workflow. If used with the `pull_request` event, updates to pull requests targeting the branch(es) listed here will trigger the workflow. This field has no effect with the `manual` event. -For example, if you'd like define a workflow that runs when commits are pushed to the `main` and `develop` branches, or when pull requests that target the `main` branch are updated, or manually, you can do so with: +For example, if you'd like to define a workflow that runs when commits are pushed to the `main` and `develop` branches, or when pull requests that target the `main` branch are updated, or manually, you can do so with: ```yaml when: -- 2.51.2