bircniandsilverwind 51368e1997 ci: use GitHub merge queue (#40130) ...

Requiring branches to be up to date reruns the full CI matrix on every
waiting PR after each merge, which saturates our 20 concurrent jobs. A
merge queue still tests against the latest `main`, but once per batch.

This runs the PR workflows on `merge_group` and reports `giteabot/lgtm`
on queue commits, since GiteaBot only sets it on PR heads. Mergers queue
PRs with "Merge when ready" instead of `reviewed/wait-merge`, so
giteabot no longer updates branches. Nothing changes until the
`merge-queue` ruleset is enabled and "Require branches to be up to date"
is turned off. Backport to `release/v28` before the ruleset covers it.

---------

Co-authored-by: silverwind <me@silverwind.io>

2026-11-01 11:23:51 +01:00

..

build-setup.md

docs: add development setup guide (#37960)

2026-06-17 06:39:22 +00:00

build-source.md

refactor!: remove go-git backend (#39487)

2026-10-03 10:04:24 +00:00

community-governance.md

ci: use GitHub merge queue (#40130)

2026-11-01 11:23:51 +01:00

development.md

docs: update AGENTS.md and dev docs (#39976)

2026-10-24 22:36:27 +00:00

guidelines-backend.md

refactor: use default error response for swagger (#40048)

2026-10-28 09:05:00 +00:00

guidelines-frontend.md

chore: update eslint and stylelint configs and re-sync modern-normalize (#38982)

2026-08-20 09:57:56 -04:00

guidelines-refactoring.md

docs: add development setup guide (#37960)

2026-06-17 06:39:22 +00:00

release-management.md

ci(release): automate signed release tags and release notes (#39544)

2026-10-06 05:21:07 +00:00

testing.md

test: run integration tests on random ports and speed up slow tests (#39842)

2026-10-18 12:56:04 +00:00