From 6605215fca50791b15b6bcbd177993a33b25a817 Mon Sep 17 00:00:00 2001 From: Ivanna Lisetska Date: Mon, 11 Mar 2024 09:23:23 -0600 Subject: [PATCH 1/4] Specified dependencies by default --- pages/pipelines/_build_states.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/pages/pipelines/_build_states.md b/pages/pipelines/_build_states.md index 30a78cdd2c..76837c2779 100644 --- a/pages/pipelines/_build_states.md +++ b/pages/pipelines/_build_states.md @@ -2,7 +2,6 @@ Build state can be one of `creating`, `scheduled`, `running`, `passed`, `failing You can query for `finished` builds to return builds in any of the following states: `passed`, `failed`, `blocked`, or `canceled`. >🚧 -> When a triggered build fails, the step that triggered it will be stuck in the running state forever. - ->📘 -> When all the steps in a build are skipped (either by using skip attribute or by using `if` condition), the build state will be marked as `not_run`. +> When a triggered build fails, the step that triggered it will be stuck in the running state forever.
+> When all the steps in a build are skipped (either by using skip attribute or by using `if` condition), the build state will be marked as `not_run`.
+By default, all steps depend on the step that uploads them, and they will not run until that one is finished. From da404e876bc1ac899dd9ec644fad9248ea3c1eec Mon Sep 17 00:00:00 2001 From: Giles Gaskell Date: Tue, 12 Mar 2024 10:35:44 +1100 Subject: [PATCH 2/4] Convert HTML in callout to Markdown (simplify contribution syntax) and remove unnecessary
elements. --- pages/pipelines/_build_states.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/pages/pipelines/_build_states.md b/pages/pipelines/_build_states.md index 76837c2779..3af8c42e2b 100644 --- a/pages/pipelines/_build_states.md +++ b/pages/pipelines/_build_states.md @@ -1,7 +1,7 @@ Build state can be one of `creating`, `scheduled`, `running`, `passed`, `failing`, `failed`, `blocked`, `canceling`, `canceled`, `skipped`, `not_run`. You can query for `finished` builds to return builds in any of the following states: `passed`, `failed`, `blocked`, or `canceled`. ->🚧 -> When a triggered build fails, the step that triggered it will be stuck in the running state forever.
-> When all the steps in a build are skipped (either by using skip attribute or by using `if` condition), the build state will be marked as `not_run`.
-By default, all steps depend on the step that uploads them, and they will not run until that one is finished. +> 🚧 +> When a [triggered build](/docs/pipelines/trigger-step) fails, the step that triggered it will be stuck in the `running` state forever. +> When all the steps in a build are skipped (either by using skip attribute or by using `if` condition), the build state will be marked as `not_run`. +> By default, all steps depend on the step that uploads them, and they will not run until that one is finished. From 99a779a90fe729038b8f6ab92232d58f1487d46d Mon Sep 17 00:00:00 2001 From: Giles Gaskell Date: Tue, 12 Mar 2024 10:39:12 +1100 Subject: [PATCH 3/4] Remove trailing space that caused the linting error. --- pages/pipelines/_build_states.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/pipelines/_build_states.md b/pages/pipelines/_build_states.md index 3af8c42e2b..91caa0154d 100644 --- a/pages/pipelines/_build_states.md +++ b/pages/pipelines/_build_states.md @@ -4,4 +4,4 @@ You can query for `finished` builds to return builds in any of the following sta > 🚧 > When a [triggered build](/docs/pipelines/trigger-step) fails, the step that triggered it will be stuck in the `running` state forever. > When all the steps in a build are skipped (either by using skip attribute or by using `if` condition), the build state will be marked as `not_run`. -> By default, all steps depend on the step that uploads them, and they will not run until that one is finished. +> By default, all steps depend on the step that uploads them, and they will not run until that one is finished. From 7c405358e49a11974aedceaab1cd614d83ee090e Mon Sep 17 00:00:00 2001 From: Giles Gaskell Date: Tue, 12 Mar 2024 10:50:33 +1100 Subject: [PATCH 4/4] Improve Markdown guidance on callouts. --- styleguides/markdown-syntax-style.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/styleguides/markdown-syntax-style.md b/styleguides/markdown-syntax-style.md index 2609e59269..15c965ee5b 100644 --- a/styleguides/markdown-syntax-style.md +++ b/styleguides/markdown-syntax-style.md @@ -211,7 +211,7 @@ A regular info callout ("purple"): ``` > 📘 An info callout title -> Callout content can have code or _emphasis_ and other inline elements in it, including links. +> Callout content can have `code` or _emphasis_ and other inline elements in it, including [internal](/docs/) or external links. > Every line break after the first becomes a new paragraph inside the callout. ``` @@ -220,7 +220,7 @@ This will be rendered as the following HTML in the site: ```

-

Callout content can have code or emphasis and other inline elements in it, including links

+

Callout content can have code or emphasis and other inline elements in it, including internal or external links.

Every line break after the first becomes a new paragraph inside the callout.

``` @@ -233,7 +233,7 @@ For troubleshooting callouts ("orange"), use the 🚧 emoji: ``` > 🚧 A troubleshooting callout title -> Callout content can have code or emphasis and other inline elements in it, including links. +> Callout content can have `code` or _emphasis_ and other inline elements in it, including [internal](/docs/) or external links. > Every line break after the first becomes a new paragraph inside the callout. ``` @@ -241,7 +241,7 @@ While no longer used in the Buildkite Docs, Work-in-progress (WIP) or Experiment ``` > 🛠 This marks it as WIP -> Callout content can have code or emphasis and other inline elements in it, including links. +> Callout content can have `code` or _emphasis_ and other inline elements in it, including [internal](/docs/) or external links. > Every line break after the first becomes a new paragraph inside the callout. ```