Anthony Wang e60158c70b Make sure API responses always refer to username in original case ... Copied from what I wrote on #19133 discussion: Handling username case is a very tricky issue and I've already encountered a Mastodon <-> Gitea federation bug due to Gitea considering Ta180m and ta180m to be the same user while Mastodon thinks they are two different users. I think the best way forward is for Gitea to only use the original case version of the username for federation so other AP software don't get confused.		2022-06-14 12:01:41 -05:00
..
api	Make sure API responses always refer to username in original case	2022-06-14 12:01:41 -05:00
common	Fix raw endpoint PDF file headers (#19825)	2022-05-28 18:10:14 +03:00
install	feat: add DEFAULT_MERGE_STYLE to `repository.pull-request` section for repo init (#19751)	2022-06-02 23:45:54 -04:00
private	Move issues related files into models/issues (#19931)	2022-06-13 17:37:59 +08:00
utils	A better go code formatter, and now `make fmt` can run in Windows (#17684)	2021-11-17 20:34:35 +08:00
web	Make sure API responses always refer to username in original case	2022-06-14 12:01:41 -05:00
init.go	Fix data-race problems in git module (quick patch) (#19934)	2022-06-11 11:56:27 +08:00