Show status check for merged PRs

[CirnoT]

This PR allows Gitea to show status check for merged PRs:

• Show status icon on PRs list for PRs whose head was removed by loading data from base repo's pull ref
• Show list of checks on PR page for merged pulls

---

[CirnoT]

Show list of checks on PR page for merged pulls

This is pretty straightforward and I don't see any potential issues with it; basically copies what non-merged PRs do

Show status icon on PRs list for PRs whose head was removed by loading data from base repo's pull ref

This is little more complicated because it changes how status is fetched for PR, maybe @zeripath could chime on on potential performance issues with this

[codecov-io]

Codecov Report

Merging #13975 (8ccc9d3) into master (66379ba) will decrease coverage by 0.00%.
The diff coverage is 58.82%.

@@            Coverage Diff             @@
##           master   #13975      +/-   ##
==========================================
- Coverage   42.20%   42.19%   -0.01%     
==========================================
  Files         710      710              
  Lines       77273    77280       +7     
==========================================
- Hits        32612    32610       -2     
- Misses      39288    39296       +8     
- Partials     5373     5374       +1     

Impacted Files	Coverage Δ
routers/repo/pull.go	31.78% <33.33%> (+0.01%)	⬆️
services/pull/pull.go	41.37% <87.50%> (+0.20%)	⬆️
modules/indexer/stats/queue.go	64.70% <0.00%> (-11.77%)	⬇️
modules/indexer/stats/db.go	43.47% <0.00%> (-8.70%)	⬇️
models/unit.go	46.57% <0.00%> (-2.74%)	⬇️
modules/queue/unique_queue_disk_channel.go	53.84% <0.00%> (-1.54%)	⬇️
models/error.go	38.49% <0.00%> (-0.49%)	⬇️
modules/git/repo_compare.go	69.36% <0.00%> (+5.40%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 66379ba...8ccc9d3. Read the comment docs.

[CirnoT]

Not sure this qualifies as kind/ui since it doesn't really touch on frontend

[zeripath]

Not sure this qualifies as kind/ui since it doesn't really touch on frontend

I think essentially this about showing stuff on the UI -> Therefore kind/ui!

[lunny]

The status information may be deleted when sometime?

[CirnoT]

The status information may be deleted when sometime?

We don't remove statuses from database (and we shouldn't, if that's what you ask for - it's a valid piece of information just like comments made by users), so unless someone were to remove it manually (in which case it will not display anything as if commit never had any statuses), no.

[lunny]

The ancient commit statuses are unuseful, especially for a big repository which has over ten thousands of commits. But they will reduce the performance of commit statuses table. So I think we should allow to delete merged or closed PR's commits statuses which haven't been merged to the git tree.

And of course, the PR is work even if the commit status deleted I think.

[CirnoT]

Yes the PR will work even if you were to allow removal of old statuses, it will just act as if there was no status and won't show anything (just like right now).

[lunny]

File conflicts

[6543]

🚀