ci: update of files from global .github repo

[asyncapi-bot]

Summary by CodeRabbit

• Chores
  • Improved the automated merging workflow by refining how merge commit messages are generated, ensuring the process accurately interprets structured data for enhanced logging precision.

[coderabbitai]

Walkthrough

This change updates a GitHub Actions workflow by modifying the environment variable used to construct the merge commit message in the automerge-for-humans job. The update switches from using a raw string output to parsing the output as JSON with the fromJSON function, affecting how the commit message is generated from the output of the create-commit-message step.

Changes

File Path	Change Summary
.github/workflows/automerge-for-humans-merging.yml	Modified MERGE_COMMIT_MESSAGE to use fromJSON(steps.create-commit-message.outputs.result) instead of a direct string output, thereby parsing the output as JSON.

Sequence Diagram(s)

sequenceDiagram
    participant Workflow as GitHub Actions Workflow
    participant Step as create-commit-message Step
    participant Parser as JSON Parser (fromJSON)
    participant Merge as Merge Commit Construction

    Workflow->>Step: Execute commit message creation
    Step-->>Workflow: Return output (JSON encoded)
    Workflow->>Parser: Parse output using fromJSON
    Parser-->>Workflow: Parsed commit message
    Workflow->>Merge: Build MERGE_COMMIT_MESSAGE with parsed content

Loading

Poem

I’m a rabbit bouncing through pipelines bright,
Hopping over code with a joyful insight.
From strings to JSON, I’ve made my quick leap,
Parsing these changes from the data so deep.
With whiskers a-twitch and ears standing tall,
I celebrate this merge—hoot, hop, and all!
🐰✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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. (Beta)
• @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.

[netlify]

✅ Deploy Preview for asyncapi-website ready!

Name	Link
🔨 Latest commit	2cef5c7
🔍 Latest deploy log	https://app.netlify.com/sites/asyncapi-website/deploys/67b7cadc4435f30008864b63
😎 Deploy Preview	https://deploy-preview-3695--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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.github/workflows/automerge-for-humans-merging.yml (1)

92-92: Ensure Valid JSON Processing for Commit Message

The modification correctly switches to using fromJSON with the steps.create-commit-message.outputs.result output. Please ensure that this output is always a valid JSON string so that the commit message is parsed correctly. If the string isn’t properly JSON-formatted, the workflow could fail or produce unintended results.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 7376ef8 and 32b9a8d.

📒 Files selected for processing (1)

• .github/workflows/automerge-for-humans-merging.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 180000ms (4)

• GitHub Check: Redirect rules - asyncapi-website
• GitHub Check: Header rules - asyncapi-website
• GitHub Check: Pages changed - asyncapi-website
• GitHub Check: Lighthouse CI