Giteabot 4c1e24864f Order pull request conflict checking by recently updated, for each push (#23220) (#23225) ... Backport #23220 When a change is pushed to the default branch and many pull requests are open for that branch, conflict checking can take some time. Previously it would go from oldest to newest pull request. Now prioritize pull requests that are likely being actively worked on or prepared for merging. This only changes the order within one push to one repository, but the change is trivial and can already be quite helpful for smaller Gitea instances where a few repositories have most pull requests. A global order would require deeper changes to queues. Co-authored-by: Brecht Van Lommel <brecht@blender.org> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>		2023-03-02 13:12:41 +08:00
..
actions
activities
admin
asymkey
auth
avatars
db
dbfs
fixtures
git
issues	Order pull request conflict checking by recently updated, for each push (#23220) (#23225)	2023-03-02 13:12:41 +08:00
migrations
organization
packages
perm
project
pull
repo
secret
system
unit
unittest
user
webhook
error.go
fixture_generation.go
fixture_test.go
main_test.go
migrate_test.go
migrate.go
org_team_test.go
org_team.go
org_test.go
org.go
repo_collaboration_test.go
repo_collaboration.go
repo_test.go
repo_transfer_test.go
repo_transfer.go
repo.go