Skip to content

Update contributer experience #5

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.

Sign up for GitHub

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

Merged
KittyChiu merged 1 commit into from
Dec 11, 2025

feat: updated contributer experience

31d814b
Select commit
Loading
Failed to load commit list.
Merged

Update contributer experience #5

feat: updated contributer experience
31d814b
Select commit
Loading
Failed to load commit list.
GitHub Advanced Security / Opengrep OSS completed Dec 11, 2025 in 3s

1 configuration not found

Warning: Code scanning may not have found all the alerts introduced by this pull request, because 1 configuration present on refs/heads/main was not found:

API upload

  • ❓  <default>

New alerts in code changed by this pull request

  • 1 note

See annotations below for details.

View all branch alerts.

Annotations

Check notice on line 33 in .github/workflows/pr-check.yml

See this annotation in the file changed.

Code scanning / Opengrep OSS

Non-deterministic Node.js version in actions/setup-node Note

Non-deterministic Node.js version pinning detected in actions/setup-node. The node-version uses a loose version specification that may resolve to different Node.js versions across workflow runs, leading to inconsistent builds. Use a semantic version with at least major version (e.g., '20', '20.11', '18.19.1') or specify node-version-file to pin to a specific Node.js version. Loose version specifications like 'lts/*', 'latest', '12.x', or 'nightly' can introduce breaking changes unexpectedly. For more guidance, see JavaScript Dependency Pinning in GitHub Actions. Submit feedback about this rule