Skip to content

Conversation

@arturfalcao
Copy link

By submitting this pull request, you agree to the terms within the Checkmarx Code of Conduct. Please review the contributing guidelines for guidance on creating high-quality pull requests.

Description

Please provide a summary of the changes and the related issue. Include relevant motivation and context.

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update

Related Issues

Link any related issues or tickets.

Checklist

  • I have performed a self-review of my code
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)
  • Any dependent changes have been merged and published in downstream modules
  • I have updated the CLI help for new/changed functionality in this PR (if applicable)
  • All active GitHub checks for tests, formatting, and security are passing
  • The correct base branch is being used

Screenshots (if applicable)

Add screenshots to help explain your changes.

Additional Notes

Add any other relevant information.

@gitguardian
Copy link

gitguardian bot commented Mar 24, 2025

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
15671991 Triggered Generic High Entropy Secret cc0acc3 internal/wrappers/client_test.go View secret
15776160 Triggered Generic High Entropy Secret cc0acc3 test/integration/scan_test.go View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secrets safely. Learn here the best practices.
  3. Revoke and rotate these secrets.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

@github-actions
Copy link

github-actions bot commented Mar 24, 2025

Logo
Checkmarx One – Scan Summary & Details525d6b98-0570-41c5-93c2-c136d10c691f

Great job, no security vulnerabilities found in this Pull Request

"testing"
)

func TestPreCommitInstall(t *testing.T) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Pls Add a test for a user that doesnt not have license to run this command

Copy link
Author

Choose a reason for hiding this comment

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

this test was added by Elchanan Arbiv can you please ask in to update ?

@arturfalcao arturfalcao force-pushed the pre-commit-hook branch 4 times, most recently from 860b75d to 40f0f09 Compare March 26, 2025 15:07
@arturfalcao arturfalcao enabled auto-merge March 27, 2025 15:02
@arturfalcao arturfalcao disabled auto-merge March 27, 2025 15:02
@cx-daniel-greenspan cx-daniel-greenspan merged commit 46492d6 into main Mar 30, 2025
9 checks passed
@cx-daniel-greenspan cx-daniel-greenspan deleted the pre-commit-hook branch March 30, 2025 06:43
cx-anjali-deore pushed a commit that referenced this pull request Jul 3, 2025
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