-
Notifications
You must be signed in to change notification settings - Fork 115
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
Conversation
🔊@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💥. |
WalkthroughThe 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 Changes
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
Assessment against linked issues
Possibly related PRs
Suggested labels
Suggested reviewers
Poem
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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
Documentation and Community
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
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. |
There was a problem hiding this 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
📒 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
- 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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🛠️ Refactor suggestion
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.
- 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 }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Which Issue(s) This PR Fixes(Closes)
Fixes #2477
Brief Description
How Did You Test This Change?
Summary by CodeRabbit