Skip to content

Conversation

@RazvanLiviuVarzaru
Copy link
Collaborator

[skip ci]

Running with skip CI to avoid mass runs.

Expected behaviour:

  • On pull requests: new pushes cancel active workflow runs
  • On main branches: only one job is allowed to run at a time.
    • If job A is running and job B is queued, pushing job C while A is still running will cancel B and queue C.

Concurrency is controlled using groups. A group is formed by a unique key based on the workflow name and Git reference (refs/).

[skip ci]

Running with skip CI to avoid mass runs.

Expected behaviour:
- On pull requests: new pushes cancel active workflow runs
- On main branches: only one job is allowed to run at a time.
  - If job A is running and job B is queued, pushing job C while A is still running will cancel B and queue C.

Concurrency is controlled using groups. A group is formed by a unique key based on the workflow name and Git reference (`refs/`).
@RazvanLiviuVarzaru
Copy link
Collaborator Author

@fauust / @grooverdan

cool / not so cool / ok / bad ?

@fauust
Copy link
Collaborator

fauust commented Jul 2, 2025

I'd like to see the results but I think that it's a great idea. Above all

On pull requests: new pushes cancel active workflow runs

Saving ressource is always a good idea.

@grooverdan
Copy link
Member

no objections.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants