go-ethereum/.github
Arran Schlosberg b0332b5168
chore(ci): add merge_group trigger to required workflows (#160)
## Why this should be merged

Allows ruleset-required workflows to be triggered by a merge queue, not
just the PR for the merge. Although `main` isn't a particularly "busy"
branch, a merge queue will ensure that CI passes on the exact version of
code that is about to be merged; i.e. (from the [docs]):

> The merge queue provides the same benefits as the **Require branches
to be up to date before merging** branch protection, but does not
require a pull request author to update their pull request branch and
wait for status checks to finish before trying to merge.

[docs]:
https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue#about-merge-queues

## How this works

Adds `merge_group` workflow trigger with [recommended
type](https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#merge_group).

## How this was tested

N/A (worst-case it has to be reverted and another PR is temporarily
blocked).
2025-03-11 13:57:57 +00:00
..
ISSUE_TEMPLATE chore(github): issue template configuration and update issue templates (#96) 2024-12-30 18:00:05 +01:00
workflows chore(ci): add merge_group trigger to required workflows (#160) 2025-03-11 13:57:57 +00:00
CODEOWNERS remove @gballet as a GraphQL codeowner (#27012) 2023-03-30 04:58:23 -04:00
CONTRIBUTING.md all: update links in documentation (#26882) 2023-03-14 10:23:49 -04:00
labels.yml chore: add label "Priority: With next Geth sync" (#129) 2025-02-11 12:41:12 +01:00
no-response.yml Change issue labels in bot configs to the new prefixed version 2018-12-14 14:50:10 +01:00
pull_request_template.md chore: PR template (#19) 2024-09-13 08:33:36 -07:00
stale.yml Change issue labels in bot configs to the new prefixed version 2018-12-14 14:50:10 +01:00