wxiaoguang e709cc76da Make Gitea always use its internal config, ignore /etc/gitconfig (#33076) ... In history, Gitea could use the system config `/etc/gitconfig` because some users said that "they might put certNonceSeed in it" Actually, we shouldn't not use it, because it also causes conflicts (there are already some fixes like #28848) To make the system clear, I think it's worth to introduce the breaking change: add `GIT_CONFIG_NOSYSTEM=1` to all git commands. ## ⚠️ BREAKING ⚠️ For most users, nothing need to do. If you have made changes to `/etc/gitconfig` to affect Gitea's behavior, you need to move these config options to Gitea's internal git config file, it is usually in Gitea's `{AppDataPath}/home/.git` directory.		2025-01-02 20:26:48 +00:00
..
consistency.go	Replace assert.Fail with assert.FailNow (#27578)	2023-10-11 11:02:24 +00:00
fixtures_loader.go	Refactor fixture loading for testing (#33024)	2024-12-30 04:06:57 +00:00
fixtures_test.go	Refactor fixture loading for testing (#33024)	2024-12-30 04:06:57 +00:00
fixtures.go	Refactor fixture loading for testing (#33024)	2024-12-30 04:06:57 +00:00
fscopy.go	Fix unittest and repo create bug (#33061)	2024-12-31 18:45:05 +08:00
reflection.go	Refactor tests (#33021)	2024-12-29 01:05:56 +00:00
testdb.go	Make Gitea always use its internal config, ignore /etc/gitconfig (#33076)	2025-01-02 20:26:48 +00:00
unit_tests.go	Refactor tests (#33021)	2024-12-29 01:05:56 +00:00