Update storing-workflow-data-as-artifacts.md#618
Conversation
No subcommand called `builds`, I know this is trying to refer to a subcommand but it's just confusing when skimming.
|
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. |
|
👋 @untitaker Thanks for opening a PR! It is a small change and your explanation in the PR template worked instead of an issue.
The tests run automatically in the checks for every PR and it looks like all of yours are passing 💚
We don't explain that anywhere, do we? I should update that in the PR template. The staging is visible by clicking the "View deployment" button, then navigating to the page you made changes to. Your changes are visible here. I'll get this triaged for review! |
lucascosti
left a comment
There was a problem hiding this comment.
LGTM! Thanks, @untitaker, I'll get this merged.
|
Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. |



Why:
No subcommand called
builds, I know this is trying to refer to a subcommand but it's just confusing when skimming.I did not open an issue beforehand because this change is trivial, so if rejected there's no sunken cost.
What's being changed:
Remove code tags around
buildsasbuildsis not literally referring to an identifierbuildsbut ratherbuild. It's just confusing.Check off the following: