Norwin

Fixing the tests was a bit tricky because the refactor in https://github.com/go-gitea/gitea/pull/19318 was a bit messy: - now that there is a separate route for issue search from the frontend,...

This is a rather unfriendly 'feature' of the API — the request needs to contain `"has_pull_requests": true` for changes to PR settings to be accepted: https://github.com/go-gitea/gitea/blob/c9c5bd88beb30b06cf52444e6515ef4c7d75993f/routers/api/v1/repo/repo.go#L834 ...as is also noted...

here's a patch to make it work without modifying the base theme. this means that the docs site will not take over future changes to the theme navbar layout, but...

@silverwind I don't know how to fix that. I have spent hours (days?) in the past trying to vertically align inputs across browsers and have given up at this point....

:eyes: I think we should just revert https://github.com/go-gitea/gitea/pull/18863 and use https://github.com/hako/durafmt instead, it also supports i18n. edit: The formatted duration is written to the comments table in the DB, so...

@wxiaoguang adjusted to use the new clone button script :)

This is a regression from https://github.com/go-gitea/gitea/pull/20454. The code for generating this page is complex as fuck, so I'm not suprised this regressed :sweat_smile:

> I don't think the quoted pr is accurate for when this was introduced. I carefully did a `git bisect`, I'm certain it's that commit. > Since it's only in...

IMO, there ideally should be at least one format that is: 1. easily human readable: grid aligned, always with header 2. easily human readable & abbreviated: same as 1, but...

I'm not well informed about the architecture, but afaik the gitea server implements migration logic for all these cases.. If so, the CLI shouldn't need to push from local disk,...