Skip to content
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

[ISSUE #2477] Update jekyll-gh-pages.yml action #2478

Merged
merged 1 commit into from
Feb 1, 2025

Conversation

mxsm
Copy link
Owner

@mxsm mxsm commented Feb 1, 2025

Which Issue(s) This PR Fixes(Closes)

Fixes #2477

Brief Description

How Did You Test This Change?

Summary by CodeRabbit

  • Chores
    • Improved the site's deployment workflow with a streamlined search indexing update.
    • Replaced the previous indexing method with a more robust process that maintains continuity even if the update encounters issues.

@rocketmq-rust-bot
Copy link
Collaborator

🔊@mxsm 🚀Thanks for your contribution🎉!

💡CodeRabbit(AI) will review your code first🔥!

Note

🚨The code review suggestions from CodeRabbit are to be used as a reference only, and the PR submitter can decide whether to make changes based on their own judgment. Ultimately, the project management personnel will conduct the final code review💥.

Copy link
Contributor

coderabbitai bot commented Feb 1, 2025

Walkthrough

The GitHub Actions workflow file responsible for deploying a Jekyll site to GitHub Pages has been updated. The previous step using the Algolia crawler has been removed and replaced with a new step that directly updates the Algolia index using the command bundle exec jekyll algolia push in the rocketmq-doc/ directory. The new step uses a secret for ALGOLIA_API_KEY and is configured to continue on error. No changes were made to exported or public entities.

Changes

File(s) Summary
.github/workflows/jekyll-gh-pages.yml Removed the Algolia crawler step; added a new step to update the Algolia index with bundle exec jekyll algolia push using a secret API key.

Sequence Diagram(s)

sequenceDiagram
    participant GH as GitHub Actions
    participant J as Jekyll Site Deployment
    participant A as Algolia Index Update

    GH->>J: Trigger build and deployment
    J->>A: Execute "bundle exec jekyll algolia push" in "rocketmq-doc/" directory
    A-->>J: Return status (step continues even on error)
    J->>GH: Complete workflow execution
Loading

Assessment against linked issues

Objective Addressed Explanation
Update jekyll-gh-pages.yml action (#2477)

Possibly related PRs

Suggested labels

feature🚀, approved

Suggested reviewers

  • TeslaRustor
  • SpaceXCN

Poem

Hoppin' through code in a digital glade,
With a skip and a jump, new changes are made.
Algolia now gets a push so bright,
Even if errors come, all is light.
From a bunny with cheer, may deployments delight!


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.

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

codecov bot commented Feb 1, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 28.62%. Comparing base (6ea703f) to head (872c05a).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2478   +/-   ##
=======================================
  Coverage   28.62%   28.62%           
=======================================
  Files         510      510           
  Lines       73518    73518           
=======================================
  Hits        21044    21044           
  Misses      52474    52474           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Contributor

@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: 1

🧹 Nitpick comments (1)
.github/workflows/jekyll-gh-pages.yml (1)

61-71: Clean up obsolete commented-out code.

The commented-out block containing the Algolia crawler configuration (lines 61-71) is now redundant due to the new direct update step. Removing this legacy code will improve clarity and maintainability. If historical context is needed, consider keeping it in version control rather than in the workflow file.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 6ea703f and 872c05a.

📒 Files selected for processing (1)
  • .github/workflows/jekyll-gh-pages.yml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (9)
  • GitHub Check: build (windows-latest, nightly)
  • GitHub Check: build (windows-latest, stable)
  • GitHub Check: build (macos-latest, nightly)
  • GitHub Check: build (macos-latest, stable)
  • GitHub Check: test
  • GitHub Check: build (ubuntu-latest, nightly)
  • GitHub Check: build
  • GitHub Check: build (ubuntu-latest, stable)
  • GitHub Check: auto-approve

Comment on lines +55 to +60
- name: Update Algolia index
working-directory: rocketmq-doc/
run: bundle exec jekyll algolia push
env:
ALGOLIA_API_KEY: ${{ secrets.ALGOLIA_API_KEY }}
continue-on-error: true
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

⚠️ Potential issue

Misplaced continue-on-error flag in the "Update Algolia index" step.

The continue-on-error: true property is placed within the env block (lines 59-60). In GitHub Actions, this flag should be a step-level property (at the same level as run and env) so that the workflow can properly continue even if the step fails.

Suggested diff:

-        env:
-          ALGOLIA_API_KEY: ${{ secrets.ALGOLIA_API_KEY }}
-          continue-on-error: true
+        continue-on-error: true
+        env:
+          ALGOLIA_API_KEY: ${{ secrets.ALGOLIA_API_KEY }}
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- name: Update Algolia index
working-directory: rocketmq-doc/
run: bundle exec jekyll algolia push
env:
ALGOLIA_API_KEY: ${{ secrets.ALGOLIA_API_KEY }}
continue-on-error: true
- name: Update Algolia index
working-directory: rocketmq-doc/
run: bundle exec jekyll algolia push
continue-on-error: true
env:
ALGOLIA_API_KEY: ${{ secrets.ALGOLIA_API_KEY }}

Copy link
Collaborator

@rocketmq-rust-bot rocketmq-rust-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@rocketmq-rust-bot rocketmq-rust-bot merged commit 9b37087 into main Feb 1, 2025
26 checks passed
@rocketmq-rust-bot rocketmq-rust-bot added approved PR has approved and removed ready to review waiting-review waiting review this PR labels Feb 1, 2025
@mxsm mxsm deleted the mxsm-patch-5 branch February 2, 2025 11:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AI review first Ai review pr first approved PR has approved auto merge enhancement⚡️ New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Enhancement⚡️] Update jekyll-gh-pages.yml action
3 participants