fix(test): isolate GPG signing key unit tests from host git config#233
Conversation
✅ Deploy Preview for devsydev canceled.
|
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
c4a905d to
e81625e
Compare
Summary
The
writeGitConfig()test helper incmd/ssh_test.gosetsHOME,XDG_CONFIG_HOME, andGIT_CONFIG_GLOBALto isolate tests from host git configuration, but does not block system-level or local repository git config from leaking through. On hosts with a GPG signing key configured (in/etc/gitconfigor the repo's.git/config), the host key corrupts test assertions.This adds
GIT_CONFIG_SYSTEMpointed to/dev/nullandGIT_DIRpointed to a fresh empty.gitdirectory in the temp home, fully isolating all sixTestGpgSigningKey_*tests from any host git configuration.