Use hash for github action

[acronhub]

What

• Pin github actions

Refs

GitHub Action supply chain attack: reviewdog/action-setup | Wiz Blog

[Copilot]

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

[gemini-code-assist]

Hello @acronhub, 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!

Summary of Changes

Hello! Gemini (gemini-code-assist) here, providing a summary of this pull request to help everyone quickly understand the changes and context.

Based on the title ("Use hash for github action") and description ("Pin github actions"), the primary intent of this pull request is to enhance the security posture of the project's GitHub Actions workflows. By pinning actions to a specific commit hash rather than a mutable tag or branch, the risk of supply chain attacks (as highlighted by the linked Wiz blog post) is significantly reduced.

Based on the provided patch context, the only file modified is the CHANGELOG.md. This update adds an entry under the 'Unreleased' section documenting the change of pinning GitHub Actions. While the patch itself doesn't show the actual workflow file modifications, the changelog entry confirms this security improvement is being introduced.

Highlights

• Security Improvement: The core purpose of this PR is to improve the security of the CI/CD pipeline by pinning GitHub Actions to specific commit hashes. This mitigates risks associated with upstream action maintainers changing code on tags/branches without notice.
• Changelog Update: The CHANGELOG.md file has been updated to include an entry for this change under the 'Unreleased' section.

Changelog

• CHANGELOG.md
  • Added an entry '- Pin github actions' under the 'Unreleased' section.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 is currently in preview and 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 to provide feedback.

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.

---

Pin the action down,
Hash secures the workflow's run,
Supply chain is safe.

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 CHANGELOG.md file to document the pinning of GitHub Actions. Pinning actions to specific commit hashes is an important security best practice to mitigate supply chain risks, as highlighted by the reference in the PR description. The changelog entry itself is concise and accurately reflects this intended improvement.

Summary of Findings

• Changelog Update Accuracy: The CHANGELOG.md has been correctly updated by adding '- Pin github actions' under the 'Unreleased' section. This entry accurately reflects the work described in the pull request's title and description.
• Documentation of Security Best Practice: The documented action of pinning GitHub Actions is a crucial security hardening measure. This PR's changelog entry appropriately records this type of improvement.
• Stylistic Suggestion (Low Severity): The changelog entry 'Pin github actions' is clear. For enhanced professionalism and consistency with product naming, 'Pin GitHub Actions' (capitalizing 'GitHub Actions') could be considered. This is a minor stylistic point, and a review comment was not added for it due to the project's review settings, which restrict comments to medium severity or higher.

Merge Readiness

The changelog update in this PR is accurate and well-formatted. From the perspective of the changes in this specific diff (which only modifies CHANGELOG.md), there are no blocking issues.

It is crucial to ensure that the actual pinning of GitHub Actions to commit hashes has been implemented in the relevant workflow files (e.g., in the .github/workflows/ directory) or will be in a related, subsequent PR, as those changes are not part of this pull request.

Assuming the underlying technical change is correctly implemented elsewhere, this changelog update is appropriate. As a reviewer, I cannot approve the PR. It should be reviewed and approved by other designated maintainers who can confirm the completeness of the related changes before merging.