You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Within a particular PR we currently run actions for every commit. Some of these are very resource heavy like integration tests.
While we might want to run these for every commit on develop and main branches, within a PR we can probably afford to cancel jobs for all but the most recent commit.
For main and developgithub.sha can be used in the group id to ensure every commit starts a job.
For feature branches github.ref in the group id to ensure all but the most recent job are cancelled.
Within a particular PR we currently run actions for every commit. Some of these are very resource heavy like integration tests.
While we might want to run these for every commit on
develop
andmain
branches, within a PR we can probably afford to cancel jobs for all but the most recent commit.For
main
anddevelop
github.sha
can be used in the group id to ensure every commit starts a job.For feature branches
github.ref
in the group id to ensure all but the most recent job are cancelled.Candidates for concurrency in PR branches are:
Example on element-ios -> element-hq/element-ios#5101
Documentation on concurrency -> https://docs.github.com/en/actions/using-jobs/using-concurrency
The text was updated successfully, but these errors were encountered: