Backport #22535

The update by rebase code reuses the merge code but shortcircuits and
pushes back up to the head. However, it doesn't set the correct pushing
environment - and just uses the same environment as the base repo. This
leads to the push update failing and thence the PR becomes out-of-sync
with the head.

This PR fixes this and adjusts the trace logging elsewhere to help make
this clearer.

Fix #18802
Signed-off-by: NAndrew Thornton <art27@cantab.net>
Signed-off-by: NAndrew Thornton <art27@cantab.net>

Signed-off-by: Njolheiser <john.olheiser@gmail.com>

Backport #22514
Co-authored-by: NBrecht Van Lommel <brecht@blender.org>

Backport #22513
Co-authored-by: NBrecht Van Lommel <brecht@blender.org>

Provide pre-compiled cgo binaries for freebsd
Co-authored-by: NJohn Olheiser <john.olheiser@gmail.com>

Backport #22512
Co-authored-by: NBrecht Van Lommel <brecht@blender.org>

Backport #22509
Co-authored-by: NSybren <122987084+drsybren@users.noreply.github.com>

Backport #22479.

When offline mode is true, we should set `disable_gravatar` to `true`
and `enable_federated_avatar` to `false` in system settings.

Signed-off-by: Njolheiser <john.olheiser@gmail.com>

Fixes #22481

_Originally posted by @zeripath in
https://github.com/go-gitea/gitea/issues/22481#issuecomment-1385188703_

Backport #22482

Fix #22480

Migration from GitBucket does not work due to a access for "Reviews" API
on GitBucket that makes 404 response.
This PR has following changes.
1. Made to stop access for Reviews API while migrating from GitBucket.
2. Added support for custom URL (e.g.
`http://example.com/gitbucket/owner/repository`)
3. Made to accept for git checkout URL
(`http://example.com/git/owner/repository.git`)
Co-authored-by: Nzeripath <art27@cantab.net>
Co-authored-by: NLunny Xiao <xiaolunwen@gmail.com>

Backport #22226
Co-authored-by: NKN4CK3R <admin@oldschoolhack.me>

Backport #22392

Fix #22386

`GetDirectorySize` moved as `getDirectorySize` because it becomes a
special function which should not be put in `util`.
Co-authored-by: NJason Song <i@wolfogre.com>

Backport #22454

There is a mistake in the code for SearchRepositoryCondition where it
tests topics as a string. This is incorrect for postgres where topics is
cast and stored as json. topics needs to be cast to text for this to
work. (For some reason JSON_ARRAY_LENGTH does not work, so I have taken
the simplest solution of casting to text and doing a string comparison.)

Ref https://github.com/go-gitea/gitea/pull/21962#issuecomment-1379584057Signed-off-by: NAndrew Thornton <art27@cantab.net>

Backport #22453

In #22447 it was noticed that display environments were not working
correctly. This was due to the setting displayMode not being set.

Further it was noticed that the error was not being displayed correctly.

This PR fixes both of these issues by forcibly setting the displayMode
setting and corrects an error in displayError.

Fix #22447
Signed-off-by: NAndrew Thornton <art27@cantab.net>

Backport #22467

Fix #22370 and more.

Before Go 1.19, the `netgo` tag for Windows does nothing.

But Go 1.19 rewrite the net package code for Windows DNS, and there is a
bug:

* https://github.com/golang/go/issues/57757

This PR just removes the `netgo` tag for Windows build, then the Gitea
for Windows can have the old DNS behavior.

Backport #21983

Fix #21772
Co-authored-by: Nwxiaoguang <wxiaoguang@gmail.com>
Co-authored-by: N花墨 <shanee@live.com>
Co-authored-by: Nwxiaoguang <wxiaoguang@gmail.com>
Co-authored-by: NLunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: NKN4CK3R <admin@oldschoolhack.me>

Backport #22449
Co-authored-by: NLauris BH <lauris@nix.lv>

Backport #22457

The API endpoints for "git" can panic if they are called on an empty
repo. We can simply allow empty repos for these endpoints without worry
as they should just work.

Fix #22452
Signed-off-by: NAndrew Thornton <art27@cantab.net>

Backport #22092

As described in the linked issue (#22091), semi-transparent UI elements
would result in JS errors due to the fact that the CSS `backgroundColor`
element was being matched by the pattern
`^rgb\((\d+),\s*(\d+),\s*(\d+)\)$`, which does not take the alpha
channel into account.

I changed the pattern to `^rgba?\((\d+),\s*(\d+),\s*(\d+).*\)$`. This
new pattern accepts both `rgb` and `rgba` tuples, and ignores the alpha
channel (that little `.*` at the end) from the sorting criteria. The
reason why I chose to ignore alpha is because when it comes to kanban
colour sorting, only the hue is important; the order of the panels
should stay the same, even if some of them are transparent.

Alternative solutions were discussed in the bug report and are included
here for completeness:
1. Change the regex from ^rgb\((\d+),\s*(\d+),\s*(\d+)\)$ to
^rgba?\((\d+),\s*(\d+),\s*(\d+)(,\s*(\d+(\.\d+)?))?\)$ (alpha channel is
a float or NaN on 5th group) and include the alpha channel in the
sorting criteria.
2. Rethink on why you're reading colours out of the CSS in the first
place, then reformat this sorting procedure.

Fix #22091
Co-authored-by: NMisterCavespider <deler.urist@tutanota.de>

Backport #22442.

Backport #21547

This PR fixes the layout of PR status layouts on mobile. For longer
status context names or on very small screens the text would overflow
and push the "Details" and "Required" badges out of the container.

Before:

![Screen Shot 2022-10-22 at 12 27

46](https://user-images.githubusercontent.com/13721712/197335454-e4decf09-4778-43e8-be88-9188fabbec23.png)

After:

![Screen Shot 2022-10-22 at 12 53

24](https://user-images.githubusercontent.com/13721712/197335449-2c731a6c-7fd6-4b97-be0e-704a99fd3d32.png)
Co-authored-by: Nkolaente <k@knt.li>
Co-authored-by: NLunny Xiao <xiaolunwen@gmail.com>

Backport #21762

Wechatwork webhook is sending the following string for pull request
reviews:

``` markdown
>
```

This commit fixes this problem.
Co-authored-by: NJim Kirisame <jim@lotlab.org>

Backport #21974

Closes #21973.

The "Actions" button on the commit view page is labelled twice in mobile
view. No other buttons on the page have a `mobile-only` extra label, so
this PR removes it.

Before:


![before](https://user-images.githubusercontent.com/6496999/204540002-75baa08a-6c06-4b39-847b-34272e09d71e.PNG)

After:


![after](https://user-images.githubusercontent.com/6496999/204539991-a0607765-d5e2-4b1a-84c9-a3e16cbc674e.PNG)
Co-authored-by: NLunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: NMark Ormesher <me@markormesher.co.uk>
Co-authored-by: NLunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: NJohn Olheiser <john.olheiser@gmail.com>

Backport #20461
Signed-off-by: NAndrew Thornton <art27@cantab.net>

Backport #22422

The current code propagates all errors up to the iteration step meaning
that a single malformed repo will prevent GC of other repos.

This PR simply stops that propagation.

Fix #21605
Signed-off-by: NAndrew Thornton <art27@cantab.net>

Backport #22146

There are a few places in FlushQueueWithContext which make an incorrect
assumption about how `select` on multiple channels works.

The problem is best expressed by looking at the following example:

```go
package main

import "fmt"

func main() {
    closedChan := make(chan struct{})
    close(closedChan)
    toClose := make(chan struct{})
    count := 0

    for {
        select {
        case <-closedChan:
            count++
            fmt.Println(count)
            if count == 2 {
                close(toClose)
            }
        case <-toClose:
            return
        }
    }
}
```

This PR double-checks that the contexts are closed outside of checking
if there is data in the dataChan. It also rationalises the WorkerPool
FlushWithContext because the previous implementation failed to handle
pausing correctly. This will probably fix the underlying problem in
 #22145

Fix #22145
Signed-off-by: NAndrew Thornton <art27@cantab.net>

backport #22199

Backport #22399

There was a serious regression in #21012 which broke the Show More
button on the diff page, and the show more button was also broken on the
file tree too.

This PR fixes this by resetting the pageData.diffFiles as the vue
watched value and reattachs a function to the show more button outside
of the file tree view.

Fix #22380
Signed-off-by: NAndrew Thornton <art27@cantab.net>

Fix #22274
Backport #22280 

This PR will allow `HOST` without port. Then a default port will be
given in future steps.

Backport #22393
Signed-off-by: Njolheiser <john.olheiser@gmail.com>

Don't display stop watch top bar icon when disabled and hidden when click other place (#22374) (#22387)

Backport #22374

Fix #22286

When timetracking is disabled, the stop watch top bar icon should be
hidden. When the stop watch recording popup, it should be allowed to
hide with some operation. Now click any place on this page will hide the
popup window.

Fix #22287
backport #22300

backport #22333

Backport of #22342 to release/v1.18 as requested

Backport #22326
Signed-off-by: Njolheiser <john.olheiser@gmail.com>

Backport https://github.com/go-gitea/gitea/pull/22318

Backport #22272.

Fix #22270.

Related to #18407.

The old code treated both sitemap and sitemap index as the format like:

```xml
...
<url>
  <loc>http://localhost:3000/explore/users/sitemap-1.xml</loc>
</url>
...
```

Actually, it's incorrect for sitemap index, it should be:

```xml
...
<sitemap>
  <loc>http://localhost:3000/explore/users/sitemap-1.xml</loc>
</sitemap>
...
```

See https://www.sitemaps.org/protocol.htmlCo-authored-by: NLauris BH <lauris@nix.lv>
Co-authored-by: Ndelvh <dev.lh@web.de>
Co-authored-by: NLunny Xiao <xiaolunwen@gmail.com>