-
Notifications
You must be signed in to change notification settings - Fork 60.7k
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
Remove mention of steps from concurrency description #36084
Conversation
Concurrency group can be defined either on a workflow level or on a job level. Steps should not be mentioned because it's not possible to control concurrency on a job step level.
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. |
👓 Previews for changed contentThis 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.
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server |
Could you please specify what to look for? I've checked the whole page for the "step" word and haven't found any other mentions. |
Thanks for opening a pull request! We've triaged this issue for technical review by a subject matter expert 👀 |
Hi @mil-dot, thanks for raising a PR—I'll get this triaged for review by a member of the 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.
Hi @mil-dot, I asked our Actions team to take a look and this, and I've made some suggestions based on readability and their feedback. The bottom line is that they agreed with your reasoning and we do want to make these changes. Unless you have any specific concerns, I'd like to apply the suggestions and merge this. Thank you!
...-workflows/choosing-what-your-workflow-does/control-the-concurrency-of-workflows-and-jobs.md
Outdated
Show resolved
Hide resolved
...-workflows/choosing-what-your-workflow-does/control-the-concurrency-of-workflows-and-jobs.md
Outdated
Show resolved
Hide resolved
…does/control-the-concurrency-of-workflows-and-jobs.md Better wording Co-authored-by: Ben Ahmady <[email protected]>
…does/control-the-concurrency-of-workflows-and-jobs.md Better wording Co-authored-by: Ben Ahmady <[email protected]>
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.
Thank you again! I'll get this merged now. Thanks for your interest in the GitHub docs, and your help
Hey @subatoi, thank you for getting this done so fast. Looks good to me, feel free to proceed at your convenience or let me know if anything else is needed from my side. |
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 ⚡ |
Concurrency group can be defined either on a workflow level or on a job level. Steps should not be mentioned because it's not possible to control concurrency on a job step level.
Why:
Closes: ISSUE_NUMBER
What's being changed (if available, include any code snippets, screenshots, or gifs):
Check off the following: