fix: add workflow to notify docs triagers on relevant PRs

[TRohit20]

Description
The PR introduces a new workflow to the website repo which runs every time a new PR is raised and checks if any .md files were modified in any manner, if yes, the workflow will auto-comment tagging docs-triagers for review and approval.

Related issue(s)
Resolves #2634

PS: Ofc, we would have to configure the secret(GH_Token) first to make this work.

[netlify]

✅ Deploy Preview for asyncapi-website ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	54e16fb
🔍 Latest deploy log	https://app.netlify.com/sites/asyncapi-website/deploys/65f58b6442d8900008fe6b6b
😎 Deploy Preview	https://deploy-preview-2660--asyncapi-website.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[asyncapi-bot]

⚡️ Lighthouse report for the changes in this PR:

Category	Score
🔴 Performance	31
🟢 Accessibility	98
🟢 Best practices	92
🟢 SEO	100
🔴 PWA	33

Lighthouse ran on https://deploy-preview-2660--asyncapi-website.netlify.app/

[quetzalliwrites]

thank you for this!

[akshatnema]

The comment made by the bot after workflow run, shouldn't be hard-coded, instead it should take the values from a json file or array that contains all the respective triager maintianers.

[anshgoyalevil]

Everything seems to be working except the fact that we do not have write permissions allowed for GH Actions in this repo
Resource not accessible by integration

@derberg I am not sure how AsyncAPI bot comments on PRs using this workflow https://github.com/asyncapi/website/blob/master/.github/workflows/lint-pr-title.yml when we don't have write permissions for GH Actions.

Do we need to add this workflow to https://github.com/asyncapi/.github/ for it to have adequate permissions?

// cc @akshatnema

[TRohit20]

@akshatnema Fixed.

@sambhavgupta0705 The workflow is currently under .github/workflows as it should be and the file placement is not a issue here. The secret in context needs to have pull request read/write access. Your question with lint PR workflow is valid to an extent. If we don't want to give the secret write access as GITHUB_TOKEN can be used in other workflows, we could create a secret called "WORKFLOW_SECRET" with write access and use the secret just for this workflow. It's not optimal though.

What do you think @derberg

[akshatnema]

https://github.com/asyncapi/website/blob/master/.github/workflows/help-command.yml#L45-L60
https://github.com/asyncapi/website/blob/master/.github/workflows/welcome-first-time-contrib.yml

@TRohit20 Can you try this approach to make a comment in PR?

[asyncapi-bot]

Hello, @akshatnema! 👋🏼

    I'm 🧞🧞🧞 Genie 🧞🧞🧞 from the magic lamp. Looks like somebody needs a hand!

    At the moment the following comments are supported in pull requests:

    - `/ready-to-merge` or `/rtm` - This comment will trigger automerge of PR in case all required checks are green, approvals in place and do-not-merge label is not added
    - `/do-not-merge` or `/dnm` - This comment will block automerging even if all conditions are met and ready-to-merge label is added
    - `/autoupdate` or `/au` - This comment will add `autoupdate` label to the PR and keeps your PR up-to-date to the target branch's future changes. Unless there is a merge conflict or it is a draft PR.

[sambhavgupta0705]

Will this work on issues also because I need to triage issues also

[TRohit20]

@sambhavgupta0705 Sure, I mean we'd probably have to add another check and event trigger to see and make it work on issues too. Possible

[sambhavgupta0705]

@TRohit20 is this ready for review?

[TRohit20]

@sambhavgupta0705 As mentioned above, the secret needs PR comment/write access to make a comment as intended, the other workflow suggested to try by @akshatnema also didn't quite seem to work.

[quetzalliwrites]

Hmm @akshatnema would a short call help?

[Shurtu-gal]

Everything seems to be working except the fact that we do not have write permissions allowed for GH Actions in this repo Resource not accessible by integration

@derberg I am not sure how AsyncAPI bot comments on PRs using this workflow https://github.com/asyncapi/website/blob/master/.github/workflows/lint-pr-title.yml when we don't have write permissions for GH Actions.

Do we need to add this workflow to https://github.com/asyncapi/.github/ for it to have adequate permissions?

// cc @akshatnema

Yeah, it needs to be added there, as far as I believe.
Better would be to create a dummy PR your own repository itself, and check if things are working.

[TRohit20]

@Shurtu-gal The GitHub script being used in latest commit is actually a reuse of what we currently have in one of our workflows as suggested by @akshatnema

[anshgoyalevil]

All parts are working great (ref). LGTM 🚀

[akshatnema]

/rtm