test: fix git_sandbox for git<2.33#713
Merged
woile merged 1 commit intocommitizen-tools:v3from Apr 19, 2023
Merged
Conversation
for old git like git-2.30 the tests broke my ~/.gitconfig file and created thousands of `name=GitHub` lines Signed-off-by: apkawa <apkawa@gmail.com>
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## v3 #713 +/- ##
==========================================
- Coverage 98.11% 97.87% -0.24%
==========================================
Files 41 42 +1
Lines 1855 1928 +73
==========================================
+ Hits 1820 1887 +67
- Misses 35 41 +6
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
for old git like git-2.30 the tests broke my ~/.gitconfig file and created thousands of
name=GitHublinesDescription
I checked the git documentation and worked out a workaround for my situation. I think it should work for a fresh git too
Checklist
./scripts/formatand./scripts/testlocally to ensure this change passes linter check and testExpected behavior
no touch my ~/.gitconfig
Steps to Test This Pull Request
run tests
Additional context
#638