Gusted 768377cb02 [GITEA] Accept shorter commit IDs in web route ... - Be more liberal in what Forgejo accepts, by reducing the minimum amount of characters for SHA to 4 characters, which is the minimum amount that Git needs in order to figure out which commit was meant. - It's safe to reduce this requirements, as commits are passed to Git which will error if the given commit ID results in more than one Git object. Forgejo will catch this error as that the Commit doesn't exist, which is a error that's already being handled in most places gracefully. - Added integration testing. - Resolves https://codeberg.org/forgejo/forgejo/issues/1760 (cherry picked from commit 0d655c7384) (cherry picked from commit 9b9aca2a02) (cherry picked from commit 0d0ab1af1f) (cherry picked from commit d3b352c854) (cherry picked from commit d6af2094df) (cherry picked from commit f96e55a7a9) (cherry picked from commit bb6261f847) (cherry picked from commit f6a4146161) (cherry picked from commit ed02921379) Conflicts: routers/web/web.go https://codeberg.org/forgejo/forgejo/pulls/2214		2024-01-22 18:13:40 +00:00
..
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