-
Notifications
You must be signed in to change notification settings - Fork 251
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Specified dependencies by default #2708
base: main
Are you sure you want to change the base?
Conversation
Preview URL: https://2708--bk-docs-preview.netlify.app |
> 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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple of minor wording tweak suggestions, even though some of this content already existed...
> 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 all the steps in a build are skipped (either by using the skip attribute or by using the `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 the uploading step is finished. |
When you said 'that one', were you referring to the uploading step?
If so, it'd be better to refer to 'that one' as 'the uploading step' to be clear what it is you're referring to as 'that one' is inherently a tad ambiguous.
I added the sentence "By default, all steps depend on the step that uploads them, and they will not run until that one is finished" to clarify the default behaviour of synchronous execution, ensuring that users understand that steps are dependent on the completion of the preceding one and may need to adjust the async attribute accordingly for parallel processing in Buildkite. This aims to prevent confusion and provide a clear understanding of the execution flow.