Skip to content

CHANGED - add concurrency to high volume workflows #5709

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

waskow-consensys
Copy link
Contributor

Description

By default, GitHub Actions allows multiple jobs within the same workflow, multiple workflow runs within the same repository, and multiple workflow runs across a repository owner's account to run concurrently. This means that multiple instances of the same workflow or job can run at the same time, performing the same steps.
https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/control-the-concurrency-of-workflows-and-jobs

GitHub Actions also allows you to disable concurrent execution. This can be useful for controlling your account’s or organization’s resources in situations where running multiple workflows or jobs at the same time could cause conflicts or consume more Actions minutes and storage than expected.

Open in GitHub Codespaces

Related issues

Fixes/Reduces: pending workflows

@waskow-consensys waskow-consensys requested a review from a team as a code owner April 24, 2025 19:08
Copy link
Contributor

@mcmire mcmire left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@waskow-consensys waskow-consensys enabled auto-merge (squash) April 25, 2025 15:35
@waskow-consensys waskow-consensys merged commit 0a2c417 into MetaMask:main Apr 25, 2025
201 of 202 checks passed
salimtb pushed a commit that referenced this pull request Apr 25, 2025
## **Description**

By default, GitHub Actions allows multiple jobs within the same
workflow, multiple workflow runs within the same repository, and
multiple workflow runs across a repository owner's account to run
concurrently. This means that multiple instances of the same workflow or
job can run at the same time, performing the same steps.

https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/control-the-concurrency-of-workflows-and-jobs

GitHub Actions also allows you to disable concurrent execution. This can
be useful for controlling your account’s or organization’s resources in
situations where running multiple workflows or jobs at the same time
could cause conflicts or consume more Actions minutes and storage than
expected.

[![Open in GitHub
Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/MetaMask/metamask-extension/pull/PR?quickstart=1)

## **Related issues**

Fixes/Reduces: pending workflows
waskow-consensys added a commit that referenced this pull request Apr 28, 2025
## Explanation

Related to #5709, this allows
concurrency on main branches to allow semantic releases.
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.

2 participants