ci: allow fork PRs to run CI

[xusd320]

This PR updates CI workflows to allow fork PRs to run CI.
Changes:

• Switched next.js submodule to HTTPS to allow public access without SSH secrets.
• Added 'permissions: contents: read' to all CI workflows.
• Optimized submodule initialization to use --recursive and --depth 1.

[gemini-code-assist]

Summary of Changes

Hello @xusd320, 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 focuses on enhancing the Continuous Integration (CI) system to support builds and tests for pull requests submitted from forks. The changes primarily involve adjusting submodule access mechanisms and configuring appropriate permissions within the CI workflows, thereby broadening the scope of automated testing to external contributions and improving the overall development workflow.

Highlights

• Submodule URL Update: The 'next.js' submodule URL has been updated from an SSH-based address to an HTTPS address. This change allows public access to the submodule without requiring SSH secrets, which is essential for enabling CI runs on fork pull requests.
• CI Permissions for Fork PRs: The 'permissions: contents: read' setting has been explicitly added to all CI workflows. This grants necessary read access to repository content for pull requests originating from forks, ensuring they can execute CI jobs successfully.
• Submodule Initialization Optimization: Submodule initialization has been optimized by incorporating '--recursive' and '--depth 1' flags. This improves the efficiency and speed of cloning submodules during CI runs.

Ignored Files

• Ignored by pattern: .github/workflows/** (12)
  • .github/workflows/biome.yml
  • .github/workflows/clippy.yml
  • .github/workflows/format.yml
  • .github/workflows/pack-ci.yml
  • .github/workflows/pack-integration.yml
  • .github/workflows/pack-release.yml
  • .github/workflows/pm-ci.yml
  • .github/workflows/pm-e2e.yml
  • .github/workflows/pm-release.yml
  • .github/workflows/taplo.yml
  • .github/workflows/utooweb-ci.yml
  • .github/workflows/utooweb-release.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 updates the .gitmodules file to use an HTTPS URL for the next.js submodule instead of SSH. This is the correct approach to allow CI workflows to run on pull requests from forks, as they do not have access to repository secrets like SSH keys. The change is sound and directly supports the PR's objective. Other changes mentioned in the description regarding CI workflows were not part of the provided diffs and could not be reviewed.