-
Notifications
You must be signed in to change notification settings - Fork 61k
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
Update outdated note on downloading actions #36370
Conversation
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.
PR Overview
This PR updates the note on downloading workflow artifacts by adding version-specific content for GitHub cloud users, while still preserving the original note for GitHub Enterprise Server users.
- Revised note for cloud users with guidance on using tokens and run identifiers.
- Conditional Markdown sections added to differentiate behavior based on the GitHub version.
Changes
File | Description |
---|---|
content/actions/writing-workflows/choosing-what-your-workflow-does/storing-and-sharing-data-from-a-workflow.md | Updated the note to include version-conditional instructions for downloading artifacts |
Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.
Comments suppressed due to low confidence (1)
content/actions/writing-workflows/choosing-what-your-workflow-does/storing-and-sharing-data-from-a-workflow.md:159
- Verify that the conditional Markdown syntax (e.g., {% ifversion %} and {% elsif %} tags) integrates with the surrounding note block and renders correctly. Consider testing the final output to ensure stability across versions.
> {% ifversion fpt or ghec %}If you want to download artifacts from a different workflow or workflow run, you need to supply a token and run identifier. See [Download Artifacts from other Workflow Runs or Repositories](https://github.com/actions/download-artifact?tab=readme-ov-file#download-artifacts-from-other-workflow-runs-or-repositories) in the documentation for the download-artifact action.
Tip: If you use Visual Studio Code, you can request a review from Copilot before you push from the "Source Control" tab. Learn more
👓 How to review these changesThank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksThe table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
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.
Just one tiny nit suggestion. 🐜 🎉
...iting-workflows/choosing-what-your-workflow-does/storing-and-sharing-data-from-a-workflow.md
Outdated
Show resolved
Hide resolved
…does/storing-and-sharing-data-from-a-workflow.md Co-authored-by: Sophie <[email protected]>
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: #36343
What's being changed (if available, include any code snippets, screenshots, or gifs):
The existing note is still correct for users of GitHub Enterprise Server, but wrong for users of Github cloud. This PR updates the note to cover the options for GitHub cloud users. See more detailed information in: #36343 (comment).
New note for Free, Pro, Team, and GitHub Enterprise Cloud versions of the docs:
The original note is still shown for GitHub Enterprise Server versions of the docs.
Check off the following: