Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

CI: a PR influx is serialised by 'require up to date' plus a 12 minute CI; consider a merge queue

Aberta
  • Algo errado?
#758 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
15/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
github, github-actions
Domínio
ci-cd

Direção de pesquisa

Start with the on: trigger block in .github/workflows/ci.yml, which needs a merge_group entry, and with the branch protection settings for main, where strict and the merge queue are configured. Maintainers must make the settings change by hand, so a newcomer's part is mainly the workflow edit and the AGENTS.md note. Done means the chosen option is applied and a test merge goes through the queue, or the maintainers record a decision in the thread.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

tech-debt

Merging 22 PRs on 2026-10-13/14 took about 15 hours of wall time, almost all of it waiting.

main has legacy branch protection with the required check All tests passed and strict: true ("require branches to be up to date before merging"). Every merge makes every other open PR stale, so each one has to be updated and re-tested (CI is 8 to 17 minutes, 12 on average, across a 15 job matrix) before it can merge, and only one PR can be in that state at a time. Roughly 12 minutes of CI times N pending PRs, serial.

Related costs seen the same day:

  • an update to a contributor's branch re-triggers GitHub's first-time-contributor approval gate for CI, so each cycle also needs a manual approval
  • a PR from a fork without "Allow edits from maintainers" cannot be updated by a maintainer at all (#719), so it waits for the author
  • retargeting a stacked PR after its base is squash-merged conflicts (add/add on the squashed file) and needs a git rebase --onto, then a close/reopen to start CI, because the workflow does not run on a base change

Options

  • GitHub merge queue: tests the PR on top of the queue head, so PRs need not be updated by hand and the queue runs them in order. Needs a merge_group trigger in .github/workflows/ci.yml and the queue enabled on main. The right fix
  • drop strict but keep the required check, accepting a possible untested combination; mitigated by CI running on main after each merge (it already does, on push)
  • if either is done, say so in AGENTS.md so tools stop assuming serial merges

A one-off relaxation of strict for a batch whose combination has been simulated is also an option, but was declined by the permission classifier as a CI bypass this time, so it has to be done by hand in the repo settings.

🤖 Generated with Claude Code

Linguagem predominante
C++
Estrelas
3.5k
Forks
639
Merge médio
1d 16h
PRs com merge (30d)
88

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de petercorke/robotics-toolbox-python

Todas as issues de petercorke/robotics-toolbox-python

Issues semelhantes

Mais issues de C++

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.