ci: update of files from global .github repo

[asyncapi-bot]

Summary by CodeRabbit

• Chores
  • Improved reliability of automated workflows triggered by merge status labels and autoupdate events.

[netlify]

✅ Deploy Preview for asyncapi-website ready!

Name	Link
🔨 Latest commit	99cfa6a
🔍 Latest deploy log	https://app.netlify.com/projects/asyncapi-website/deploys/69fdbc7c5e56680008204ab2
😎 Deploy Preview	https://deploy-preview-5389--asyncapi-website.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

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

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: dff70610-e44d-4085-a1f6-dab8269f1aac

📥 Commits

Reviewing files that changed from the base of the PR and between bd774ae and 99cfa6a.

📒 Files selected for processing (1)

• .github/workflows/automerge-for-humans-add-ready-to-merge-or-do-not-merge-label.yml

---

📝 Walkthrough

Walkthrough

The automerge GitHub Actions workflow is updated to use a bot PAT (secrets.GH_TOKEN) instead of github.token in three jobs' github-script steps, enabling downstream workflows triggered by labeled events to execute properly.

Changes

Workflow Authentication

Layer / File(s)	Summary
Token Configuration Updates .github/workflows/automerge-for-humans-add-ready-to-merge-or-do-not-merge-label.yml	The "ready-to-merge", "do-not-merge", and "autoupdate" jobs now pass secrets.GH_TOKEN to github-script steps instead of github.token, with comments explaining the PAT is used to allow downstream labeled-event workflows to run.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 A token swap, so neat and tidy,
Bot PAT flows on Friday,
Downstream workflows now take flight,
Labels trigger just right! 🏷️✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title is vague and generic, referring to 'update of files from global .github repo' without specifying what changes were actually made or their impact.	Replace the generic title with a specific description of the main change, such as: 'ci: use bot PAT for GitHub Actions workflows to enable downstream job triggering' or 'ci: update automerge workflow to use GH_TOKEN for event propagation'.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch bot/update-files-from-global-repo

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[asyncapi-bot]

⚡️ Lighthouse report for the changes in this PR:

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

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