Skip to content

ci(workflows): remove the mobile build and release script from git-action #2891

New issue

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

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

Already on GitHub? # to your account

Merged
merged 1 commit into from
Feb 12, 2025

Conversation

zzcr
Copy link
Member

@zzcr zzcr commented Feb 12, 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

  • Chores

    • Streamlined the automated build workflows by removing the mobile theme build steps, ensuring a simplified and efficient deployment process.
  • Style

    • Applied minor formatting improvements to configuration files for better consistency.

Copy link

coderabbitai bot commented Feb 12, 2025

Walkthrough

This pull request removes the "Run Build ThemeMobile" step from four GitHub Actions workflow files, thereby modifying the build control flow for the publish processes. The change excludes the ThemeMobile component from the build sequence while leaving all other steps unaltered. Additionally, a newline was appended at the end of packages/vue/package.json for proper formatting.

Changes

File(s) Change Summary
.github/workflows/auto-all-publish.yml, .github/workflows/dispatch-all-publish-alpha.yml, .github/workflows/dispatch-renderless-theme-publish(-alpha).yml Removed the Run Build ThemeMobile step, altering the build control flow in the publish workflows.
packages/vue/package.json Appended a newline at the end of the file for consistent formatting.

Sequence Diagram(s)

sequenceDiagram
    participant Trigger as CI Trigger
    participant Checkout as Code Checkout
    participant Setup as Setup Dependencies
    participant Builder as Build Steps
    participant Publisher as Component Publisher

    Trigger->>Checkout: Start workflow
    Checkout->>Setup: Checkout and setup environment
    Setup->>Builder: Execute build steps (excluding ThemeMobile)
    Builder->>Publisher: Publish built components
Loading

Possibly related PRs

Suggested labels

ci

Suggested reviewers

  • kagol

Poem

I hopped through workflows, light and free,
Dropping old steps for a fresher spree.
No more mobile theme build to see,
Just a cleaner flow, as neat as can be.
With every commit I cheer with glee,
A rabbit’s joy in every line—yee!
🐰✨


📜 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 b952e35 and c85ed1f.

📒 Files selected for processing (5)
  • .github/workflows/auto-all-publish.yml (0 hunks)
  • .github/workflows/dispatch-all-publish-alpha.yml (0 hunks)
  • .github/workflows/dispatch-renderless-theme-publish-alpha.yml (0 hunks)
  • .github/workflows/dispatch-renderless-theme-publish.yml (0 hunks)
  • packages/vue/package.json (1 hunks)
💤 Files with no reviewable changes (4)
  • .github/workflows/dispatch-all-publish-alpha.yml
  • .github/workflows/dispatch-renderless-theme-publish.yml
  • .github/workflows/auto-all-publish.yml
  • .github/workflows/dispatch-renderless-theme-publish-alpha.yml
✅ Files skipped from review due to trivial changes (1)
  • packages/vue/package.json

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

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

Walkthrough

此PR移除了GitHub Actions中的移动端构建和发布脚本,涉及多个工作流文件的修改,主要是删除相关的构建和发布步骤。

Changes

文件 概要
.github/workflows/auto-all-publish.yml 删除了移动端构建和发布的相关步骤。
.github/workflows/dispatch-all-publish-alpha.yml 删除了移动端构建和发布的相关步骤。
.github/workflows/dispatch-renderless-theme-publish-alpha.yml 删除了移动端构建和发布的相关步骤。
.github/workflows/dispatch-renderless-theme-publish.yml 删除了移动端构建和发布的相关步骤。
packages/vue/package.json 更新了依赖版本。

Copy link

[e2e-test-warn]
The component to be tested is missing.

The title of the Pull request should look like "fix(vue-renderless): [action-menu, alert] fix xxx bug".

Please make sure you've read our contributing guide

@zzcr zzcr merged commit 78a3774 into dev Feb 12, 2025
14 checks passed
@kagol kagol deleted the ci-removue-mobile-0212 branch April 14, 2025 12:26
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant