Skip to content

ci(workflow): fix path matching rules to ensure only component directories are matched #3364

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 29, 2025

Conversation

zzcr
Copy link
Member

@zzcr zzcr commented Apr 28, 2025

修正路径匹配规则以确保只匹配组件目录

PR

PR Checklist

Please check if your PR fulfills the following requirements:

  • The commit message follows our Commit Message Guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

Summary by CodeRabbit

  • Style

    • Minor adjustment to the description text in the alert component demo for improved consistency.
    • Updated the title text in the mobile demo HTML page.
  • Chores

    • Refined workflow rules in GitHub Actions to more accurately detect changes in component directories.

Copy link

coderabbitai bot commented Apr 28, 2025

Walkthrough

This update includes three main changes: a refinement of regular expression patterns in a GitHub Actions workflow to more precisely match component directories, a minor textual adjustment in the description of a Vue component example, and a modification to the title text in an HTML file for a mobile demo page. No changes were made to the logic, structure, or public interfaces of any components or scripts.

Changes

File(s) Change Summary
.github/workflows/test-e2e-pr.yml Updated regex patterns in workflow to require trailing slashes when matching component directories.
examples/sites/demos/pc/app/alert/basic-usage.vue Modified the description text of a tiny-alert component by removing a space in the string.
examples/sites/mobile.html Changed the HTML document title text by adding a character at the end.

Poem

Hop, hop, a regex tune—
Patterns tightened, none too soon.
A space removed, a title grown,
In code and docs, the changes shown.
With every tweak, the garden’s neat—
The rabbit’s work is quick and sweet! 🐇✨

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

examples/sites/demos/pc/app/alert/basic-usage.vue

Oops! Something went wrong! :(

ESLint: 8.57.1

ESLint couldn't find the plugin "eslint-plugin-vue".

(The package "eslint-plugin-vue" was not found when loaded as a Node module from the directory "".)

It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

npm install eslint-plugin-vue@latest --save-dev

The plugin "eslint-plugin-vue" was referenced from the config file in ".eslintrc.js » @antfu/eslint-config » @antfu/eslint-config-vue".

If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team.


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

Copy link

@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 (2)
.github/workflows/test-e2e-pr.yml (1)

46-58: Remove trailing spaces to satisfy YAML lint
Several pattern lines have trailing spaces after the comma, which YAMLLint flags as errors. Trimming these spaces will resolve the lint issues.
Apply this diff:

-                pattern: /^packages\/renderless\/src\/([^/]+)\//, 
+                pattern: /^packages\/renderless\/src\/([^/]+)\//,
-                pattern: /^packages\/vue\/src\/([^/]+)\//, 
+                pattern: /^packages\/vue\/src\/([^/]+)\//,
-                pattern: /^examples\/sites\/demos\/pc\/app\/([^/]+)\//, 
+                pattern: /^examples\/sites\/demos\/pc\/app\/([^/]+)\//,
🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 46-46: trailing spaces

(trailing-spaces)


[error] 51-51: trailing spaces

(trailing-spaces)


[error] 52-52: trailing spaces

(trailing-spaces)


[error] 57-57: trailing spaces

(trailing-spaces)


[error] 58-58: trailing spaces

(trailing-spaces)

examples/sites/demos/pc/app/alert/basic-usage.vue (1)

9-9: Consistent spacing in description attribute
The description for the “simple” type was updated to type 为simple, removing the space between and simple. Other examples use a space (e.g., type 为 success), so for readability and consistency consider description="type 为 simple".

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 666bb0f and 850191b.

📒 Files selected for processing (3)
  • .github/workflows/test-e2e-pr.yml (1 hunks)
  • examples/sites/demos/pc/app/alert/basic-usage.vue (1 hunks)
  • examples/sites/mobile.html (1 hunks)
🧰 Additional context used
🪛 YAMLlint (1.35.1)
.github/workflows/test-e2e-pr.yml

[error] 46-46: trailing spaces

(trailing-spaces)


[error] 51-51: trailing spaces

(trailing-spaces)


[error] 52-52: trailing spaces

(trailing-spaces)


[error] 57-57: trailing spaces

(trailing-spaces)


[error] 58-58: trailing spaces

(trailing-spaces)

🔇 Additional comments (5)
.github/workflows/test-e2e-pr.yml (4)

46-49: Restrict component matching to directories
The updated regex anchored at ^packages/renderless/src/([^/]+)/ with a trailing slash ensures you only detect component directories (and their subpaths), preventing files like package.json from being matched.

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 46-46: trailing spaces

(trailing-spaces)


52-55: Consistent directory-only regex for Vue components
Adding the trailing slash in the ^packages/vue/src/([^/]+)/ pattern brings it in line with the renderless rule, so only Vue component folders (not individual files) are captured.

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 52-52: trailing spaces

(trailing-spaces)


56-61: Example demo pattern – only match directories
The new rule ^examples/sites/demos/pc/app/([^/]+)/ with the slash now correctly targets demo component folders under app/ and skips files (e.g., basic-usage.vue still maps to the alert directory, but files like package.json won’t trigger a match).

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 57-57: trailing spaces

(trailing-spaces)


[error] 58-58: trailing spaces

(trailing-spaces)


62-67: Theme components – enforce directory matching
By requiring the trailing slash in ^packages/theme/src/([^/]+)/, you ensure theme component directories (and their nested files) are detected, while standalone files are excluded.

examples/sites/mobile.html (1)

7-7: Verify the updated HTML document title
The title was changed to “TinyVueMobile 演示是”. Please confirm this text is grammatically correct in Chinese and consistent with other demo pages.

@zzcr zzcr merged commit 9f4f99a into dev Apr 29, 2025
5 checks passed
@zzcr zzcr deleted the fix-e2e-test-error-0428 branch April 29, 2025 01:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant