Skip to content

fix: security gemini-cli SHA-pin + LICENSE rename + gitignore complete#204

Merged
DavidKRK merged 3 commits into
gh-pagesfrom
fix-security-april2026
Apr 24, 2026
Merged

fix: security gemini-cli SHA-pin + LICENSE rename + gitignore complete#204
DavidKRK merged 3 commits into
gh-pagesfrom
fix-security-april2026

Conversation

@DavidKRK
Copy link
Copy Markdown
Owner

Sécurité + docs standards :

✅ gemini-cli.yml : SHA-pin run-gemini-cli@v0.1.10 → @06123c6a203eb7a964ce3be7c48479cc66059f23
✅ license.txt → LICENSE (reconnu par GitHub)
✅ .gitignore complété (node_modules/, .DS_Store, etc.)

Ready to merge.

Copilot AI review requested due to automatic review settings April 21, 2026 13:50
@bolt-new-by-stackblitz
Copy link
Copy Markdown

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request significantly expands the .gitignore file to cover various environments, logs, and build outputs, and adds an MIT License file. Feedback highlights a discrepancy where expected security updates to gemini-cli.yml are missing from the commit. Furthermore, the addition of the MIT License while the original GPL license file remains creates a legal ambiguity that needs to be addressed by removing the old license or clarifying the change.

Comment thread .gitignore
# Local Netlify folder
.netlify
E
# Dependencies
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

security-high high

Le titre et la description de la pull request indiquent une mise à jour de sécurité (SHA-pinning) pour le fichier gemini-cli.yml, mais ce fichier n'apparaît pas dans les modifications de cette PR. Veuillez vérifier si vous avez oublié d'inclure ce fichier dans votre commit.

Comment thread LICENSE
@@ -0,0 +1,21 @@
MIT License
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

La description indique que license.txt est renommé en LICENSE. Cependant, le fichier license.txt (sous licence GPL) est toujours présent dans le dépôt, alors que ce nouveau fichier LICENSE introduit une licence MIT. Cette situation crée une ambiguïté juridique. Il est recommandé de supprimer l'ancien fichier et de confirmer que le changement de licence est intentionnel.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR aims to improve repo hygiene and supply-chain security by SHA-pinning the Gemini CLI GitHub Action, standardizing the repository license filename for GitHub detection, and expanding .gitignore to cover common local/build artifacts.

Changes:

  • Pin google-github-actions/run-gemini-cli to a specific commit SHA in the gemini-cli workflow.
  • Add a top-level LICENSE file with MIT text.
  • Expand .gitignore to ignore common dependency, OS, editor, log, env, and build output files.

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 1 comment.

File Description
LICENSE Adds MIT license text under the conventional LICENSE filename.
.gitignore Replaces the minimal ignore list with a more complete set of common ignores.
.github/workflows/gemini-cli.yml Replaces the action tag with a commit SHA to harden against supply-chain changes.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread LICENSE
Comment on lines +1 to +4
MIT License

Copyright (c) 2024 DavidKRK

@DavidKRK
Copy link
Copy Markdown
Owner Author

@copilot je réponds quoi ? Current change ? Incoming ou both ?

Copy link
Copy Markdown
Contributor

Copilot AI commented Apr 24, 2026

@copilot je réponds quoi ? Current change ? Incoming ou both ?

It's neither — no merge conflict here. The issue was simply that license.txt (the old file) wasn't deleted when LICENSE was added. I've removed license.txt in commit 52a1470, so now there's only one authoritative license file (LICENSE) which GitHub will detect correctly.

@DavidKRK
Copy link
Copy Markdown
Owner Author

@copilot
Je répond quoi
<<<<< fix-security-april2026
uses: 'google-github-actions/run-gemini-cli@06123c6a203eb7a964ce3be7c48479cc66059f23' # ratchet:v0.1.10

    uses: 'google-github-actions/run-gemini-cli@06123c6a203eb7a964ce3be7c48479cc66059f23' # ratchet:google-github-actions/run-gemini-cli@v0.1.10

gh-pages

Copy link
Copy Markdown
Contributor

Copilot AI commented Apr 24, 2026

@copilot
Je répond quoi
<<<<< fix-security-april2026
...

Choose Incoming (gh-pages). Both versions use the same SHA pin (the security fix is preserved either way), but the incoming comment # ratchet:google-github-actions/run-gemini-cli@v0.1.10 is the correct full format for the ratchet tool — it includes the action owner/name, which is required for ratchet to update it automatically in the future.

@DavidKRK DavidKRK merged commit 8258e6e into gh-pages Apr 24, 2026
9 of 10 checks passed
@DavidKRK DavidKRK deleted the fix-security-april2026 branch April 24, 2026 23:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants