This is just the agenda for the meeting at 14:00 - 14:30 (CEST). Join via https://meet.google.com/zih-cgjz-czo
Follow up on last week’s issues
Anything updated within the past week can be ignored during triage. If someone wants to discuss a specific issue/PR then it should be added to the agenda.
I’d propose we discuss adding required checks to the repository. See About protected branches - GitHub Docs for more about this. The short summary is that we can say that a check like
build-html must pass, otherwise the PR can’t be merged.
I have pushed to 3.4 and broke GHA:
It’s fixed now.
We’ve applied branch protection on master. It now requires the
build-web status checks to pass, otherwise you can’t merge. While we generally trust reviewers to not merge when it’s broken, this also prevents merging when GitHub Actions for some reason doesn’t run at all. This also prevents (accidental) force pushes to master.
It was not applied on stable branches because it would break our cherry pick workflow.
- Went over a few PRs and provided more context to some issues