Fix readme generation releases

[goruha]

what

• Fix readme generation releases

Summary by CodeRabbit

• Chores
  • Simplified pull request label automation rules for auto updates by removing a redundant condition. No changes to user-facing functionality.

[coderabbitai]

Walkthrough

The pull request updates the .github/mergify.yml configuration file by removing a redundant nested condition from the "Set no-release and skip-changelog labels for auto updates" rule. Specifically, it deletes the condition that required both "files=README.md" and "#files=1" within an "and" clause, simplifying the rule. No other logic or actions in the Mergify configuration are changed.

Changes

File(s)	Change Summary
.github/mergify.yml	Removed a redundant nested condition involving README.md from a pull request rule for labeling.

Sequence Diagram(s)

sequenceDiagram
    participant PR as Pull Request
    participant Mergify as Mergify Bot

    PR->>Mergify: PR triggers label rule
    alt PR matches simplified auto-update file conditions
        Mergify->>PR: Add 'no-release' and 'skip-changelog' labels
    else PR does not match
        Mergify->>PR: No action
    end

Loading

Possibly related PRs

• Simplify merrgify config #147: Simplifies .github/mergify.yml by removing redundant or nested conditions, similar to this PR.
• Improve mergify workflow #115: Refines the same Mergify rule by simplifying its condition, indicating a direct connection.
• Added readme auto merge #180: Adjusts auto-merge and labeling rules for README.md, which relates to the condition removed in this PR.

Suggested labels

needs-test

Suggested reviewers

• cloudpossebot

Poem

In the garden of YAML, I hop with delight,
Pruning the rules to keep logic light.
No more nested tangles for README to see—
Just a simpler path for Mergify and me!
With every hop, the configs grow clean,
A tidy file makes this rabbit serene.
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0e013e0 and cd6a030.

📒 Files selected for processing (1)

• .github/mergify.yml (0 hunks)

💤 Files with no reviewable changes (1)

• .github/mergify.yml

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: Mergify Merge Protections
• GitHub Check: Summary

---

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

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

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

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

[mergify]

Important

Cloud Posse Engineering Team Review Required

This pull request modifies files that require Cloud Posse's review. Please be patient, and a core maintainer will review your changes.

To expedite this process, reach out to us on Slack in the #pr-reviews channel.

[github-actions]

These changes were released in v1.2.4.