Clarify the existing pending job is canceled

[zachborboacryptofi]

Why:

Docs clarification.

Closes: N/A

Check off the following:

• I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

  • For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

• For content changes, I have completed the self-review checklist.

[welcome]

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.

[nguyenalex836]

@zachborboacryptofi Thank you for opening a PR! ✨ Can you elaborate on what you are hoping to clarify by adding the word "existing" to the reusable? 💛

[zachborboacryptofi]

@nguyenalex836 Hi. I think adding "existing" to the pending job will help clarify the documentation, as the current wording can be a bit confusing. The update emphasizes that we're referring to any pending job or workflow that's already in place that will be canceled and not the new incoming pending job or workflow, which should make it clearer for readers.

As currently written, it reads like this:

in-progress: myConcurrencyGroup1.job1
pending: myConcurrencyGroup1.job2

+

myConcurrencyGroup1.job3

=

in-progress: myConcurrencyGroup1.job1
pending: (empty, as _any_ pending jobs or workflows were canceled)

By emphasizing that the existing pending job, if it exists, is canceled, it reads like this:

in-progress: myConcurrencyGroup1.job1
pending: myConcurrencyGroup1.job2

+

myConcurrencyGroup1.job3

=

in-progress: myConcurrencyGroup1.job1
pending: myConcurrencyGroup1.job3

[nguyenalex836]

@zachborboacryptofi Thank you for the elaboration! I'll triage this for review so that we can get a writer to weigh in on this change as well 💛

[github-actions]

Thanks for opening a pull request! We've triaged this issue for technical review by a subject matter expert 👀

[nguyenalex836]

@zachborboacryptofi Thank you for those final updates! We'll get this merged 🍏

[github-actions]

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 ⚡