Skip to content

feat: GitHub CI concurrency #2807

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

Kryptos-FR
Copy link
Member

@Kryptos-FR Kryptos-FR commented May 29, 2025

PR Details

Automatically cancels running workflow if a more recent push or merge happened.

This should save some actions minutes by preventing to build for commits that are no longer relevant.

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

Types of changes

  • Docs change / refactoring / dependency upgrade
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist

  • My change requires a change to the documentation.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • I have built and run the editor to try this change out.

@Kryptos-FR Kryptos-FR self-assigned this May 29, 2025
@VaclavElias
Copy link
Contributor

That's clever. I didn't know such feature is available.

@Kryptos-FR Kryptos-FR added the enhancement New feature or request label May 29, 2025
@Kryptos-FR Kryptos-FR merged commit 2003364 into stride3d:master Jun 2, 2025
2 of 11 checks passed
@Kryptos-FR Kryptos-FR deleted the feature/github-ci-concurrency branch June 2, 2025 11:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-Build enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants