Do not pin the action

[5ouma]

⚠️ Issue

close #

✏️ Description

It changes so quickly.

🔄 Type of the Change

• 🎉 New Feature
• 🧰 Bug
• 🛡️ Security
• 📖 Documentation
• 🏎️ Performance
• 🧹 Refactoring
• 🧪 Testing
• 🔧 Maintenance
• 🎽 CI
• 🧠 Meta

• I agree to follow the Code of Conduct.

Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.

[coderabbitai]

Walkthrough

The pull request introduces modifications to the GitHub Actions workflow configuration file .github/workflows/pre-commit.yml. The changes involve reformatting the branches specification from a single-line to a multi-line array format and updating the pre-commit action reference from a specific commit hash to the main branch of the repository. These modifications do not fundamentally alter the workflow's core functionality but represent a stylistic and referencing update.

Changes

File	Change Summary
.github/workflows/pre-commit.yml	- Reformatted branches specification to multi-line format - Updated pre-commit action reference from specific commit hash to main branch

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1ef6b10 and 4b042c2.

📒 Files selected for processing (1)

• .github/workflows/pre-commit.yml (2 hunks)

🧰 Additional context used

🪛 GitHub Check: CodeQL

.github/workflows/pre-commit.yml

[warning] 15-15: Unpinned tag for a non-immutable Action in workflow
Unpinned 3rd party Action '🚸 pre-commit' step Uses Step uses '5ouma/utils/pre-commit' with ref 'main', not a pinned commit hash

🔇 Additional comments (2)

.github/workflows/pre-commit.yml (2)

5-6: LGTM: Branch specification formatting

The multi-line YAML format improves readability.

---

15-15: ⚠️ Potential issue

Critical: Pin the action to a specific commit hash

Using @main for third-party actions is a security risk as the action could be modified unexpectedly. This could potentially introduce malicious code into your CI pipeline.

Let's verify the action's commit history to help select a stable version:

Revert to using a specific commit hash:

-        uses: 5ouma/utils/pre-commit@main
+        uses: 5ouma/utils/pre-commit@973639b350016dec6fe7f665f4650d22ea1935d5

References:

• GitHub Actions Security Hardening

✅ Verification successful

Confirmed: Action should be pinned to commit 973639b

The review comment is correct. Pin the action to the latest stable commit:

-        uses: 5ouma/utils/pre-commit@main
+        uses: 5ouma/utils/pre-commit@973639b350016dec6fe7f665f4650d22ea1935d5

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check the commit history of the action repository
gh api \
  -H "Accept: application/vnd.github+json" \
  -H "X-GitHub-Api-Version: 2022-11-28" \
  repos/5ouma/utils/commits \
  --jq '.[0:5] | .[] | {sha: .sha, date: .commit.author.date, message: .commit.message}'

Length of output: 1488

🧰 Tools

🪛 GitHub Check: CodeQL

[warning] 15-15: Unpinned tag for a non-immutable Action in workflow
Unpinned 3rd party Action '🚸 pre-commit' step Uses Step uses '5ouma/utils/pre-commit' with ref 'main', not a pinned commit hash

---

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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.