Uh oh!
There was an error while loading. Please reload this page.
Document reusable workflow limitation - #11831
Conversation
I discovered that reusable workflows do not support the `strategy` property and that was not documented anywhere.
Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
Automatically generated comment ℹ️This comment is automatically generated and will be overwritten every time changes are committed to this branch. The table contains an overview of files in the Content directory changesYou may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.
|
ramyaparimi
commented
Nov 11, 2021
@cmitz |
skedwards88
commented
Nov 30, 2021
Closing via #11830 (comment) |
skedwards88
left a comment
There was a problem hiding this comment.
Thank you for this PR (and for the clarifying issue)! I added a suggestion to clarify that this just applies to jobs that call another workflow. I'll go ahead an incorporate the suggestion then get this merged down for you.
Uh oh!
There was an error while loading. Please reload this page.
Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡ |
Why:
Closes#11830
I discovered that reusable workflows do not support the
strategyproperty and that was not documented anywhere. So, I added that to the list of limitations.That issue, however, still needs to be confirmed.
What's being changed:
Very little is being changed. Just one line with a limitation was added to an existing list.
Check off the following:
Writer impact (This section is for GitHub staff members only):