We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
looks like due to the following, git is trying to look at /.config/git/attributes
/.config/git/attributes
berry/packages/plugin-patch/sources/patchUtils.ts
Lines 292 to 295 in 3c8a90a
Removing the HOME var fixes it, but obviously it's not a solution since that cold introduce issue with reproducibility
HOME
Maybe setting HOME to an empty tmp dir could help? Or maybe there is some env var that could be set which would prevent git from looking for .config?
this only started happening when I ungraded my system (and git to 2.47.1) so maybe just running patch-commit with this version is enough
System: OS: Linux 6.12 cpe:/o:nixos:nixos:25.05 25.05 (Warbler) CPU: (16) x64 Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz Binaries: Node: 22.12.0 - /nix/store/k1r91cjalyc2mzzllpv5hklhqn8wvgjr-nodejs-22.12.0/bin/node Yarn: 4.7.0 - /nix/store/8ms3a80bfa05i69fj68alyg7c97rbjp7-yarn-berry/bin/yarn npm: 10.9.0 - /nix/store/k1r91cjalyc2mzzllpv5hklhqn8wvgjr-nodejs-22.12.0/bin/npm
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Self-service
Describe the bug
looks like due to the following, git is trying to look at
/.config/git/attributes
berry/packages/plugin-patch/sources/patchUtils.ts
Lines 292 to 295 in 3c8a90a
Removing the
HOME
var fixes it, but obviously it's not a solution since that cold introduce issue with reproducibilityMaybe setting HOME to an empty tmp dir could help? Or maybe there is some env var that could be set which would prevent git from looking for .config?
To reproduce
this only started happening when I ungraded my system (and git to 2.47.1) so maybe just running patch-commit with this version is enough
Environment
Additional context
No response
The text was updated successfully, but these errors were encountered: