Skip to content

git-secrets --install test failures without code changes #239

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.

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

Closed
sparr opened this issue Jun 16, 2023 · 0 comments · Fixed by #221
Closed

git-secrets --install test failures without code changes #239

sparr opened this issue Jun 16, 2023 · 0 comments · Fixed by #221

Comments

@sparr
Copy link
Contributor

sparr commented Jun 16, 2023

I believe that all tests passed when I last contributed to this repo, both before and after my change. I have confirmed that the following failure happens now with the current master branch and with commit b9e96b3 prior to the last change. I suspect this could be caused by some change to my bash, git, grep, etc, but I haven't been able to narrow it down yet.

 ✗ Overwrites hooks if -f is given
   (in test file test/git-secrets.bats, line 147)
     `[ $status -eq 0 ]' failed
   Initialized empty Git repository in /tmp/test-repo/.git/
   /home/clrnc/src/git-secrets
   /tmp/test-repo
   /tmp/test-repo
 ✓ installs hooks for repo with Debian style directories
 ✗ installs hooks to template directory
   (in test file test/git-secrets.bats, line 164)
     `[ $status -eq 0 ]' failed
   Initialized empty Git repository in /tmp/test-repo/.git/
   /home/clrnc/src/git-secrets
   /tmp/test-repo

The failure on line 147 which tests line 146 is late. There's actually a NZEC on line 145 which isn't currently being tested for.

Both failures are related to git-secrets --install

@sparr sparr changed the title Test failures without code changes git-secrets --install test failures without code changes Jun 16, 2023
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 a pull request may close this issue.

1 participant