docs
docs copied to clipboard
Clarify private repo hosted reusable workflows
Why:
Closes #22434
What's being changed (if available, include any code snippets, screenshots, or gifs):
Remove the conditional statements that mask informing GitHub Team users of the possibility that private repositories can in fact host reusable workflows for an organization.
Check off the following:
- [ ] I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
- [ ] For content changes, I have completed the self-review checklist.
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.
It isn't clear to me if this is a "feature" for a paid account or if it's also available for free. The "version" selector for docs puts "Free, Pro, Team" all together. Perhaps more should be added in this PR to clarify any nuance around this.
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.
| Source | Preview | Production | What Changed |
|---|---|---|---|
actions/using-workflows/reusing-workflows.md |
fpt ghec ghes@ 3.7 3.6 3.5 3.4 ghae |
fpt ghec ghes@ 3.7 3.6 3.5 3.4 ghae |
fpt: Free, Pro, Team ghec: GitHub Enterprise Cloud ghes: GitHub Enterprise Server ghae: GitHub AE
@TannerPerrien Thanks for opening an issue and submitting a PR! I've edited your post slightly to link to your issue.
I'll get this triaged for review! :zap:
Closing as per https://github.com/github/docs/issues/22434#issuecomment-1340404669