mirror of
https://codeberg.org/forgejo/forgejo.git
synced 2024-11-14 18:24:14 +01:00
d3769a6cdc
It does not pollute the output because they go to sqlite-log/gitea.log and it may provide clues for debugging. When trying to figure out a problem in production, Debug is likely to be used but in a development environment a very fine grain log is the most useful. If that's really too much noise, the lines can be trimmed by removing all those with [T]. (cherry picked from commit |
||
---|---|---|
.. | ||
e2e | ||
fuzz | ||
gitea-lfs-meta | ||
gitea-repositories-meta | ||
integration | ||
testdata/data/attachments/a/0 | ||
mssql.ini.tmpl | ||
mysql.ini.tmpl | ||
pgsql.ini.tmpl | ||
sqlite.ini.tmpl | ||
test_utils.go |