-
Notifications
You must be signed in to change notification settings - Fork 62.2k
Add link to context availability for workflow .if
key syntax
#22437
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
Conversation
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. |
@MarkIannucci Thank you for opening a PR and linking it to your issue! ✨ I'll get this triaged for review! ⚡ |
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.
fpt: Free, Pro, Team |
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.
Thanks for this PR, @MarkIannucci! I've pushed up a change that adds a link to the context availability article for all the mention of .if
keys.
Almost all keys are somewhat restricted in their use of certain contexts, but it is more obvious when using them for conditions in the .if
keys, so I think a regular sentence will suffice here.
Thanks for the contribution, I'll get this merged.
.if
key syntax
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 ⚡ |
I like how you toned down my frustration. I also saw some nice practices in the way the docs team is using actions to deliver the docs site. I definitely feel that I learned more than I gave with this PR. Thank you :) |
Why:
Closes #22436
What's being changed (if available, include any code snippets, screenshots, or gifs):
Check off the following: