Skip to content

Conversation

@asyncapi-bot
Copy link
Contributor

@asyncapi-bot asyncapi-bot commented Jul 28, 2025

Summary by CodeRabbit

  • Chores
    • Updated internal workflow for sending email notifications. No changes to user-facing features or functionality.

@netlify
Copy link

netlify bot commented Jul 28, 2025

Deploy Preview for asyncapi-website ready!

Name Link
🔨 Latest commit 5393a30
🔍 Latest deploy log https://app.netlify.com/projects/asyncapi-website/deploys/688d0a8a94ac540009fac813
😎 Deploy Preview https://deploy-preview-4282--asyncapi-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

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

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 28, 2025

Walkthrough

The GitHub Actions workflow was updated to pass the event title to the Mailchimp email script via an environment variable (TITLE) instead of as a direct string argument. The script now receives only the URL as an argument, while accessing the title from the environment. No changes were made to control flow or logic.

Changes

Cohort / File(s) Change Summary
Workflow Email Notification Update
.github/workflows/notify-tsc-members-mention.yml
Modified workflow to pass event title as TITLE environment variable to the Mailchimp email script, instead of as a direct argument. Script now receives only the URL as an argument. Applied consistently across all notification steps.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested labels

autoapproved, autoupdate

Suggested reviewers

  • derberg
  • akshatnema
  • anshgoyalevil
  • sambhavgupta0705
  • Mayaleeeee
  • devilkiller-ag
  • vishvamsinh28
  • asyncapi-bot-eve
  • Siddhant-Pragyan-Sinha

Poem

🐰✨
In the warren of workflows, a tweak hops through—
Passing titles by env, not by string, as we do.
The script sniffs its title from air,
While URLs ride arguments fair.
A gentle change, a bunny’s delight,
Email hops onward, workflow just right!
🌱💌

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • 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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@asyncapi-bot
Copy link
Contributor Author

asyncapi-bot commented Jul 28, 2025

⚡️ Lighthouse report for the changes in this PR:

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

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

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
.github/workflows/notify-tsc-members-mention.yml (1)

69-74: DRY-up the duplicated Mailchimp step to cut maintenance overhead
The 6 jobs repeat the same npm install + actions/github-script duo with only the URL differing. Consider:
 • extracting this into a composite action or
 • turning the workflow into a reusable one called with uses: ./ from job-specific wrappers.
This removes copy-paste drift risk when the Mailchimp script or its env list changes.

Also applies to: 115-120, 161-166, 207-212, 253-258, 299-304

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c17e431 and 4ad659b.

📒 Files selected for processing (1)
  • .github/workflows/notify-tsc-members-mention.yml (6 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: akshatnema
PR: asyncapi/website#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.
Learnt from: asyncapi-bot
PR: asyncapi/website#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
Learnt from: anshgoyalevil
PR: asyncapi/website#3950
File: scripts/utils/check-locales.ts:122-129
Timestamp: 2025-04-20T16:05:16.482Z
Learning: In the AsyncAPI website project, Next.js throws errors at runtime when locale files are missing, making additional validation for missing files unnecessary in the check-locales script.
Learnt from: anshgoyalevil
PR: asyncapi/website#3557
File: tests/fixtures/markdown/check-edit-links-data.js:3-11
Timestamp: 2025-01-19T04:51:41.255Z
Learning: In the AsyncAPI website repository, the test data in `tests/fixtures/markdown/check-edit-links-data.js` intentionally includes inconsistent paths (with and without 'docs' prefix) to verify the script's ability to normalize and handle ambiguous path structures.
Learnt from: akshatnema
PR: asyncapi/website#3265
File: tests/fixtures/toolsObjectData.js:51-52
Timestamp: 2024-10-09T17:35:36.557Z
Learning: When reviewing code in the 'asyncapi/website' repository, akshatnema prefers that I do not provide committable code suggestions.
Learnt from: akshatnema
PR: asyncapi/website#3423
File: tests/index.test.js:2-7
Timestamp: 2025-01-18T08:44:43.614Z
Learning: In the AsyncAPI website project, JavaScript test files must include the .ts extension when importing TypeScript files (e.g., `require('../scripts/build-rss.ts')`). This is a project-specific requirement enforced by the linting rules and build setup, even though it differs from typical Node.js behavior.
Learnt from: bandantonio
PR: asyncapi/website#3393
File: markdown/blog/socketio-part2.md:506-506
Timestamp: 2024-11-13T20:40:29.580Z
Learning: When performing rebranding updates, there's no need to update the titles of bug reports in `dashboard.json`, even if they contain the old name.
Learnt from: anshgoyalevil
PR: asyncapi/website#3557
File: scripts/markdown/check-editlinks.js:58-59
Timestamp: 2025-01-08T15:15:00.759Z
Learning: In the AsyncAPI codebase, batch processing operations (like in the Dashboard script and check-editlinks.js) follow a sequential pattern using await in loops, which is the preferred approach for maintaining consistency across the codebase.
.github/workflows/notify-tsc-members-mention.yml (2)

Learnt from: akshatnema
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.

Learnt from: asyncapi-bot
PR: asyncapi/website#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
⏰ 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). (2)
  • GitHub Check: Automerge PR autoapproved by a bot
  • GitHub Check: Lighthouse CI
🔇 Additional comments (1)
.github/workflows/notify-tsc-members-mention.yml (1)

69-74: TITLE env wiring looks good
Switching to an environment variable and reading it via process.env.TITLE is correct and keeps the JS call clean. No issues spotted with this specific injection.

@sambhavgupta0705
Copy link
Member

@coderabbitai why we are not able to merge it

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 28, 2025

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check the PR status and merge requirements
gh pr view 4282 --json state,mergeable,mergeStateStatus,statusCheckRollup,reviewDecision,isDraft,baseRefName,headRefName

# Check if there are any failing status checks
gh pr checks 4282

# Check for any merge conflicts
gh pr view 4282 --json mergeable

# Check repository branch protection rules for the target branch
gh api repos/asyncapi/website/branches/master/protection --jq '.required_status_checks, .required_pull_request_reviews, .enforce_admins'

Length of output: 7162


🏁 Script executed:

#!/bin/bash
# Check the labels on the PR which might affect automerge
gh pr view 4282 --json labels

# Look at the automerge workflow to understand why it's being skipped
cat .github/workflows/automerge-for-bots.yml

# Check if there are any blocking labels or conditions
gh pr view 4282 --json labels,assignees,requestedReviewers

Length of output: 1073


🏁 Script executed:

#!/bin/bash
# Find automerge workflow files
find .github/workflows -name "*automerge*" -o -name "*bot*" | head -10

# Check if there are any blocking labels
gh pr view 4282 --json labels,assignees,reviewRequests

# Check if there's a do-not-merge label or similar blocking condition
gh pr view 4282 --json labels | jq -r '.labels[].name' | grep -i "merge\|block\|hold"

Length of output: 1032


🏁 Script executed:

#!/bin/bash
# Check the main automerge workflow
cat .github/workflows/automerge.yml

# Also check the automerge for humans workflow that shows as successful
cat .github/workflows/automerge-for-humans-merging.yml

Length of output: 6169


@sambhavgupta0705 The PR cannot be merged because it's currently blocked by several conditions:

Current Status Analysis

The PR shows mergeStateStatus: "BLOCKED" despite:

  • ✅ All checks passing
  • ✅ Being approved
  • ✅ Having no merge conflicts
  • ✅ Having the "autoapproved" label

Why It's Blocked

  1. Bot Automerge Failed: The "Autoapprove PR comming from a bot" workflow was skipped, which means the automatic bot approval process didn't complete properly. This caused the subsequent "Automerge PR autoapproved by a bot" step to also be skipped.

  2. Pending Review Requests: The PR has multiple pending review requests from maintainers:

    • derberg
    • akshatnema
    • anshgoyalevil
    • sambhavgupta0705 (you)
    • Mayaleeeee
    • devilkiller-ag
    • vishvamsinh28
  3. Missing Ready-to-Merge Label: For manual merge via the "Automerge For Humans" workflow, the PR needs a "ready-to-merge" label, which it currently doesn't have.

Solutions

You can unblock this PR by either:

Option 1: Add the ready-to-merge label to trigger the human automerge workflow
Option 2: Manually merge the PR since you have maintainer permissions
Option 3: Use the /ready-to-merge command (based on the learnings I have about supported PR commands)

Since this is an automated update from the global .github repo and all checks are passing, I'd recommend using the /ready-to-merge command or adding the ready-to-merge label.


⛔ Permission issue

There was a permission issue. Please ask the repository administrator to refresh CodeRabbit's permissions at https://github.com/apps/coderabbitai/installations/55584500.


🧠 Learnings used
Learnt from: akshatnema
PR: asyncapi/website#3265
File: tests/fixtures/toolsObjectData.js:51-52
Timestamp: 2024-10-09T17:35:36.557Z
Learning: When reviewing code in the 'asyncapi/website' repository, akshatnema prefers that I do not provide committable code suggestions.

Learnt from: asyncapi-bot
PR: asyncapi/website#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

Learnt from: akshatnema
PR: asyncapi/website#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.

Learnt from: anshgoyalevil
PR: asyncapi/website#3950
File: scripts/utils/check-locales.ts:122-129
Timestamp: 2025-04-20T16:05:16.482Z
Learning: In the AsyncAPI website project, Next.js throws errors at runtime when locale files are missing, making additional validation for missing files unnecessary in the check-locales script.

Learnt from: anshgoyalevil
PR: asyncapi/website#3557
File: tests/fixtures/markdown/check-edit-links-data.js:3-11
Timestamp: 2025-01-19T04:51:41.255Z
Learning: In the AsyncAPI website repository, the test data in `tests/fixtures/markdown/check-edit-links-data.js` intentionally includes inconsistent paths (with and without 'docs' prefix) to verify the script's ability to normalize and handle ambiguous path structures.

Learnt from: akshatnema
PR: asyncapi/website#3423
File: tests/index.test.js:2-7
Timestamp: 2025-01-18T08:44:43.614Z
Learning: In the AsyncAPI website project, JavaScript test files must include the .ts extension when importing TypeScript files (e.g., `require('../scripts/build-rss.ts')`). This is a project-specific requirement enforced by the linting rules and build setup, even though it differs from typical Node.js behavior.

@asyncapi-bot
Copy link
Contributor Author

@derberg @devilkiller-ag @akshatnema @sambhavgupta0705 @vishvamsinh28 @anshgoyalevil @Mayaleeeee Please take a look at this PR. Thanks! 👋

@derberg
Copy link
Member

derberg commented Jul 29, 2025

@sambhavgupta0705 I looked into it a bit

for future remember you can see all codecov runs transparently in https://app.codecov.io/gh/asyncapi/website/pulls

fun for https://app.codecov.io/gh/asyncapi/website/pull/4282 says: Missing Head Commit. Unable to compare commits because the head commit was not found.

this is blocking status update here in PR, so the PR cannot be merged as it is waiting for codecov, which is required check before merging

@sambhavgupta0705
Copy link
Member

I think I should close it

@akshatnema akshatnema deleted the bot/update-files-from-global-repo branch August 3, 2025 13:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants