feat: migrate to Cloudflare pages

[fi3ework]

1. migrate to Cloudflare
2. drop Rspress preview
3. set cron job to 12h interval by GitHub Actions

[netlify]

❌ Deploy Preview for rstack-ecosystem-ci failed. Why did it fail? →

Name	Link
🔨 Latest commit	e966ae1
🔍 Latest deploy log	https://app.netlify.com/projects/rstack-ecosystem-ci/deploys/696f5bca03242300087b8671

[gemini-code-assist]

Summary of Changes

Hello @fi3ework, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request transitions the project's website hosting infrastructure from Netlify to Cloudflare Pages. This strategic move streamlines deployment processes by eliminating Netlify-specific configurations and build functions. Concurrently, it removes the Rspress preview feature, which was previously integrated with Netlify, and updates the website's internal scheduling mechanism to use a more precise, UTC-based 12-hour cron for updates.

Highlights

• Infrastructure Migration: The project's website hosting has been migrated from Netlify to Cloudflare Pages, removing all Netlify-specific configurations and deployment mechanisms.
• Rspress Preview Removal: The Rspress preview functionality, previously integrated with Netlify, has been completely removed from the test suite and the frontend UI.
• Enhanced Scheduling Logic: The website's update scheduling mechanism has been refactored to be more precise and UTC-aware, now operating on a 12-hour cron schedule with improved countdown formatting.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Ignored Files

• Ignored by pattern: .github/workflows/** (4)
  • .github/workflows/cloudflare-pages-deploy.yml
  • .github/workflows/rspress-ecosystem-ci-from-commit.yml
  • .github/workflows/rspress-ecosystem-ci-from-pr.yml
  • .github/workflows/rspress-ecosystem-ci-selected.yml

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request effectively migrates the project from Netlify to Cloudflare Pages by removing Netlify-related configurations, deployment scripts, and associated UI elements. The update also includes a change in the deployment schedule from hourly to twice daily, with the frontend logic correctly adjusted to reflect this. The code changes are clean and well-implemented. I have one suggestion to enhance the efficiency of the new scheduling logic.