Update jekyll-gh-pages.yml

[mxsm]

Which Issue(s) This PR Fixes(Closes)

Fixes #issue_id

Brief Description

How Did You Test This Change?

Summary by CodeRabbit

• New Features
  • Introduced an enhanced search crawler that improves content indexing and search accuracy.
• Chores
  • Streamlined the website deployment process for greater efficiency and faster performance.

[coderabbitai]

Walkthrough

This pull request updates the GitHub Actions workflow for deploying a Jekyll site. It removes several steps related to repository checkout, Ruby setup, Bundler caching, dependency installation, and Algolia index updates. In their place, a new step is added to the deployment job that creates and triggers an Algolia crawler using specified secret parameters. The modifications shift the focus from Ruby setup in the build process to integrating Algolia’s crawling functionality directly after the site deployment.

Changes

File(s)	Change Summary
.github/workflows/jekyll-gh-pages.yml	Removed steps for repository checkout (full fetch), Ruby setup, Bundler caching/installation, and Algolia index update; added a new step "Algolia crawler creation and crawl" with parameters (crawler-user-id, crawler-api-key, algolia-app-id, algolia-api-key, crawler-name, site-url, override-config).

Sequence Diagram(s)

sequenceDiagram
    participant D as Deployment Job
    participant GP as GitHub Pages
    participant AC as Algolia Crawler Action

    D->>GP: Deploy Jekyll site to GitHub Pages
    GP-->>D: Confirm deployment
    D->>AC: Trigger Algolia crawler creation and crawl
    AC-->>D: Initiate crawling process

Loading

Possibly related PRs

• [ISSUE #2450]Add Algolia Crawler Github Action #2451: Introduces the Algolia crawler step in the deployment workflow.
• [ISSUE #2452]Update Add Algolia Crawler Github Action crawler-name #2453: Focuses on modifying the Algolia crawler parameters within the same workflow step.
• [ISSUE #2463]🔨Update jekyll-gh-pages.yml action #2464: Adjusts the configuration of the Algolia crawler step in the workflow file.

Suggested labels

feature🚀, enhancement⚡️

Suggested reviewers

• TeslaRustor
• SpaceXCN

Poem

I'm a happy rabbit on a code-bound spree,
Hopping through changes as swift as can be.
Out with the old, and in with a new call,
Algolia's crawler now leads the ball.
May our workflows leap and dance with glee! 🐇🚀

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 477c0ad and 1dff904.

📒 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: build
• GitHub Check: build (ubuntu-latest, nightly)
• GitHub Check: test
• GitHub Check: build (ubuntu-latest, stable)
• GitHub Check: auto-approve

🔇 Additional comments (1)

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

55-66: Algolia Crawler Step Integration

The newly added "Algolia crawler creation and crawl" step is correctly integrated within the deploy job. All required parameters—including the secret-based credentials and crawler configuration—are clearly provided. Please verify that the crawler name and site URL values are up-to-date and that the repository settings include the expected secret values. Overall, the modifications streamline the deployment by removing unnecessary Ruby/Bundler steps while adding this targeted post-deployment action.

---

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

[rocketmq-rust-bot]

🔊@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💥.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 28.62%. Comparing base (477c0ad) to head (1dff904).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2488   +/-   ##
=======================================
  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.

[rocketmq-rust-bot]

LGTM