Skip to content

Conversation

@Mrtenz
Copy link
Member

@Mrtenz Mrtenz commented Oct 27, 2025

Explanation

This adds the merge_group trigger to the main workflow, so we can enable the merge queue.

References

Checklist

  • I've updated the test suite for new or updated code as appropriate
  • I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
  • I've communicated my changes to consumers by updating changelogs for packages I've changed, highlighting breaking changes as necessary
  • I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes

Note

Add the merge_group trigger to the main GitHub Actions workflow to enable merge queue runs.

Written by Cursor Bugbot for commit e67a294. This will update automatically on new commits. Configure here.

@Mrtenz Mrtenz requested a review from a team as a code owner October 27, 2025 10:05
cursor[bot]

This comment was marked as outdated.

@Mrtenz Mrtenz force-pushed the mrtenz/enable-merge-queue branch from 61582fe to ffb79fe Compare October 27, 2025 10:12
@Mrtenz Mrtenz enabled auto-merge (squash) October 27, 2025 10:13
@Mrtenz Mrtenz force-pushed the mrtenz/enable-merge-queue branch from ffb79fe to e67a294 Compare October 27, 2025 10:19
@Mrtenz Mrtenz merged commit 096a5c6 into main Oct 27, 2025
255 checks passed
@Mrtenz Mrtenz deleted the mrtenz/enable-merge-queue branch October 27, 2025 10:25
Gudahtt added a commit that referenced this pull request Oct 27, 2025
@Gudahtt Gudahtt mentioned this pull request Oct 27, 2025
4 tasks
Gudahtt added a commit that referenced this pull request Oct 27, 2025
Gudahtt added a commit that referenced this pull request Oct 27, 2025
## Explanation

Revert #6948 and #6949, which updated the GitHub Action workflows to
support the merge queue.

We are considering leaving the merge queue enabled, but we're reverting
this for now until we can explore it further. Specifically there was a
risk identified with our release process that we'd like to mitigate
first (where it might be possible for a release to include unreviewed
changes if it's merged with something ahead of it in the queue).

## References

Reverts #6948 and #6949

## Checklist

- [x] I've updated the test suite for new or updated code as appropriate
- [x] I've updated documentation (JSDoc, Markdown, etc.) for new or
updated code as appropriate
- [x] I've communicated my changes to consumers by [updating changelogs
for packages I've
changed](https://github.com/MetaMask/core/tree/main/docs/contributing.md#updating-changelogs),
highlighting breaking changes as necessary
- [x] I've prepared draft pull requests for clients and consumer
packages to resolve any breaking changes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants