ci: update of files from global .github repo

[asyncapi-bot]

Summary by CodeRabbit

• Chores
  • Internal workflow improvements and documentation updates to maintain code quality standards.

[coderabbitai]

Walkthrough

Four GitHub workflow YAML files were updated to include inline comments and NOSONAR annotations on Slack markdown conversion action usages. No functional behavior changes were introduced; these are purely documentation and linting enhancements.

Changes

Cohort / File(s)	Summary
GitHub Workflows - Slack Action Annotations \.github/workflows/automerge-orphans.yml, \.github/workflows/issues-prs-notifications.yml, \.github/workflows/notify-tsc-members-mention.yml, \.github/workflows/release-announcements.yml	Added inline comments and NOSONAR tags to slackify-markdown@master action references across workflow definitions. No changes to control flow or action behavior.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Repetitive, consistent pattern across all files (documentation annotations only)
• No functional logic changes to review
• No impact on workflow execution or behavior

Suggested reviewers

• derberg
• akshatnema
• anshgoyalevil
• sambhavgupta0705
• Mayaleeeee
• devilkiller-ag
• vishvamsinh28

Poem

A rabbit hops through workflows fine,
With NOSONAR tags in a tidy line—
No logic changed, just notes so clear,
The linter's worries disappear! 🐰✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'ci: update of files from global .github repo' accurately describes the main changes across all workflow files, which involve updates and NOSONAR annotations added to CI/CD workflow files from a global repository.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

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

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7d42caf and 1175568.

📒 Files selected for processing (4)

• .github/workflows/automerge-orphans.yml (1 hunks)
• .github/workflows/issues-prs-notifications.yml (3 hunks)
• .github/workflows/notify-tsc-members-mention.yml (6 hunks)
• .github/workflows/release-announcements.yml (1 hunks)

🧰 Additional context used

🧠 Learnings (4)

📓 Common learnings

Learnt from: asyncapi-bot
Repo: asyncapi/website PR: 0
File: :0-0
Timestamp: 2025-02-18T12:07:42.211Z
Learning: The following PR commands are supported in the asyncapi/website repository:
- `/please-take-a-look` or `/ptal`: Requests attention from reviewers who haven't reviewed the PR
- `/ready-to-merge` or `/rtm`: Triggers automerge when all conditions are met
- `/do-not-merge` or `/dnm`: Blocks automerge even if all conditions are met
- `/autoupdate` or `/au`: Adds autoupdate label to keep PR in sync with target branch
- `/update` or `/u`: One-time update of PR with latest changes from target branch

📚 Learning: 2024-11-25T18:34:51.303Z

Learnt from: akshatnema
Repo: asyncapi/website PR: 3378
File: scripts/markdown/check-markdown.js:1-1
Timestamp: 2024-11-25T18:34:51.303Z
Learning: When reviewing `scripts/markdown/check-markdown.js`, optimizations should be addressed in separate issues and not included in the current pull request.

Applied to files:

• .github/workflows/issues-prs-notifications.yml

📚 Learning: 2024-11-25T18:41:29.632Z

Learnt from: akshatnema
Repo: asyncapi/website PR: 3378
File: scripts/markdown/check-markdown.js:1-1
Timestamp: 2024-11-25T18:41:29.632Z
Learning: When updating workflows for the AsyncAPI website repository, use `.github/workflows/if-nodejs-pr-testing.yml` to include environment variables and secrets for Node.js PR testing.

Applied to files:

• .github/workflows/issues-prs-notifications.yml
• .github/workflows/notify-tsc-members-mention.yml

📚 Learning: 2025-02-18T12:07:42.211Z

Learnt from: asyncapi-bot
Repo: asyncapi/website PR: 0
File: :0-0
Timestamp: 2025-02-18T12:07:42.211Z
Learning: The following PR commands are supported in the asyncapi/website repository:
- `/please-take-a-look` or `/ptal`: Requests attention from reviewers who haven't reviewed the PR
- `/ready-to-merge` or `/rtm`: Triggers automerge when all conditions are met
- `/do-not-merge` or `/dnm`: Blocks automerge even if all conditions are met
- `/autoupdate` or `/au`: Adds autoupdate label to keep PR in sync with target branch
- `/update` or `/u`: One-time update of PR with latest changes from target branch

Applied to files:

• .github/workflows/issues-prs-notifications.yml
• .github/workflows/notify-tsc-members-mention.yml

⏰ Context from checks skipped due to timeout of 180000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)

• GitHub Check: Redirect rules - asyncapi-website
• GitHub Check: Header rules - asyncapi-website
• GitHub Check: Pages changed - asyncapi-website
• GitHub Check: cypress-run

🔇 Additional comments (1)

.github/workflows/automerge-orphans.yml (1)

55-56: Clarify the rationale for NOSONAR suppression and @master reference.

The addition of # //NOSONAR suggests that SonarQube analysis is flagging a specific warning or vulnerability concern on this line. While the documentation comment explains that referencing @master is "safe," this approach deviates from GitHub Actions best practices, which recommend pinning to a specific commit SHA for reproducibility and security.

Since these files are centrally managed and auto-synced, I assume this reflects an intentional upstream decision. However, it would be helpful to document what specific issue the NOSONAR tag is suppressing.

---

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

[netlify]

✅ Deploy Preview for asyncapi-website ready!

Name	Link
🔨 Latest commit	2ddec61
🔍 Latest deploy log	https://app.netlify.com/projects/asyncapi-website/deploys/6933054cbbdf5c0008d5e7bd
😎 Deploy Preview	https://deploy-preview-4612--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 project configuration.

[asyncapi-bot]

⚡️ Lighthouse report for the changes in this PR:

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

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

[princerajpoot20]

/rtm

[princerajpoot20]

/rtm