test: skip ci on markdown file changes

[gitcommitshow]

Summary by CodeRabbit

• Chores
  • Updated workflow triggering conditions to refine when tests are run.

[coderabbitai]

Warning

Rate Limit Exceeded

@gitcommitshow has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 15 minutes and 15 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.
Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.
Please see our FAQ for further information.

Commits

Files that changed from the base of the PR and between d9944c6 and 6f6ac8d.

Walkthrough

The recent update focuses on refining the conditions under which the automated workflow is triggered. By eliminating the push event for the main branch and specifying paths to ignore during pull_request events, the modification aims to streamline the workflow's activation, ensuring it runs only under more relevant circumstances.

Changes

File	Summary
.github/workflows/test.yml	Removed push event for main branch; added ignored paths for pull_request event

🐰✨
In the realm of code, where changes abound,
A rabbit hopped in, and a tweak it found.
"No more needless runs," it said with glee,
For efficiency's sake, we all agree.
So hop, skip, and a jump, the workflow's refined,
With every little change, better we're aligned. 🌟
🐰✨

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>.
  • Generate unit-tests 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 tests 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 1f49a5a and d9944c6.

Files selected for processing (1)

• .github/workflows/test.yml (1 hunks)

Additional comments: 1

.github/workflows/test.yml (1)

• 10-13: The addition of paths-ignore with Markdown files (**.md), ENV_SAMPLE, and LICENSE is a good approach to optimize CI runs by skipping unnecessary workflow triggers. This change aligns well with the PR's objective to enhance CI efficiency by preventing workflow runs for changes that do not affect the software's functionality. However, it's important to ensure that all relevant non-code files are included in this list to maximize efficiency. Additionally, consider if there are any scenarios where changes to these ignored files might indirectly affect the build or test processes, and if so, document these exceptions or reconsider the ignored paths.