Skip to content

Conversation

@LuisDuarte1
Copy link
Contributor

Summary

Add more context on when dynamic step names might work. They always do as long they are built in a deterministic manner, this wasn't very explicit before and caused some confusion in users.

Documentation checklist

@github-actions github-actions bot added size/s product:workflows Workflows: https://developers.cloudflare.com/workflows/ labels Nov 5, 2024
Copy link
Contributor

@sidharthachatterjee sidharthachatterjee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you, left a suggestion

Co-authored-by: Sidhartha Chatterjee <[email protected]>
@sidharthachatterjee sidharthachatterjee merged commit 1b9cb71 into cloudflare:production Nov 5, 2024
7 checks passed
@LuisDuarte1 LuisDuarte1 deleted the lduarte/better-dynamic-step-name-explanation branch November 5, 2024 17:35
elithrar pushed a commit that referenced this pull request Nov 6, 2024
* feat: [workflows] clarify when dynamic step names can be used

* Apply suggestions from code review

Co-authored-by: Sidhartha Chatterjee <[email protected]>

---------

Co-authored-by: Sidhartha Chatterjee <[email protected]>
harshil1712 pushed a commit that referenced this pull request Dec 3, 2024
* feat: [workflows] clarify when dynamic step names can be used

* Apply suggestions from code review

Co-authored-by: Sidhartha Chatterjee <[email protected]>

---------

Co-authored-by: Sidhartha Chatterjee <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

product:workflows Workflows: https://developers.cloudflare.com/workflows/ size/s

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants