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 that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.

Content directory changes

You 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.

fpt: Free, Pro, Team
ghec: GitHub Enterprise Cloud
ghes: GitHub Enterprise Server

@MizouziE Thanks so much for opening a PR! I'll get this triaged for review ✨

Hi @MizouziE, and thanks for your PR—

I'm afraid we won't be accepting this submission on this occasion:

• The reusable you're proposing to update is only used in articles after where we'd expect this kind of disclaimer would be useful. For example, you can see under "Workflow basics" in "About workflows" that we say that a workflow "must contain" one or more jobs
• The language "one or more", in any case, already implies that a minimum of one should be present

Thank you for your interest in the GitHub docs!

Thanks for the reply and explanation @subatoi I appreciate your points. Just wanted to mention that it's possible that people land directly on the pages which are beyond the points addressed in the Workflow basics chapters (as was my case) and, as is always the case with documentation, that leaves the reader with a little less context than ideal.

Anyway, lesson learned and hopefully I'll form a better habit of gathering context beyond the scope of what it is I'm attempting to do.

Thanks for your engagement @MizouziE—I've reached out to the internal team in question with your feedback, and they may choose to take it further and make some amendments.

Please don't be discouraged from raising further contributions—just as a gentle point, it may help to raise an issue first next time, so we can have this kind of discussion there first.