use gh issue comment instead of peter-evans/create-or-update-comment

[jcbhmr]

Why:

Closes: #29419

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

• I have reviewed my changes in staging, available via the View deployment link in this PR's timeline.

  • 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.

[github-actions]

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/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md	fpt ghec ghes@ 3.10 3.9 3.8 3.7 3.6 ghae	fpt ghec ghes@ 3.10 3.9 3.8 3.7 3.6 ghae

---

fpt: Free, Pro, Team
ghec: GitHub Enterprise Cloud
ghes: GitHub Enterprise Server
ghae: GitHub AE

[cmwilson21]

@jcbhmr Thank you for opening a PR and linking it to your issue! ✨

I'll get this triaged for review! ⚡

[peterbe]

I'm not a Docs content reviewer but I endorse the idea of switching the third-party action to instead using the gh CLI.

I left some nits for the reviewer.

[jcbhmr]

i forgot to mention that this pr also happens to fix this bug:

if: github.event.label.name == 'help-wanted'

👆 doesn't work since the label name is "help wanted" not "help-wanted" and so it never triggers 😢

if: github.event.label.name == 'help wanted'

👆 this works ✅
its whatever name appears here:

so this one has "waiting for review" right now but NOT "waiting-for-review". you can check this in the search by clicking on it and seeing whats in the search box/query:

"waiting for review" NOT "waiting-for-review"

idk if there are other spots like this in other parts of the documentation too 🤷‍♀️

[skedwards88]

Thanks for this PR! I love this change. I left a few minor comments that I'll go ahead an incorporate, then we'll get this merged for you.

[jcbhmr]

turns out the workflow does need the --repo flag lol 🤣

vs with the --repo flag

i think its down to that gh needs a .git folder (current git repo context) to figure out which remote github repo it corresponds to. if there isn't one then i think you're always required to specify it manually via -R/--repo. 🤷‍♂️

[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 ⚡