Closed afoley587 closed 3 days ago
The changes introduce a concurrency control mechanism to the GitHub Actions workflow in .github/workflows/pr.yml
. A concurrency
section is added to manage simultaneous executions by grouping workflows based on their names and Git references, allowing for cancellation of in-progress runs when a new run is triggered. The existing jobs remain mostly unchanged, with conditions maintained for their execution, while the teams
job is temporarily disabled.
File | Change Summary |
---|---|
.github/workflows/pr.yml |
Added a concurrency section to manage simultaneous executions and allow cancellation of in-progress runs. The teams job is temporarily disabled. Existing job conditions are maintained. |
.github/workflows/pr.yml
file and involve job dependencies and conditions for job execution, which are closely related to the concurrency control mechanism introduced in the main PR.ci
In the workflow's dance, a new step we find,
Concurrency added, to leave old runs behind.
With jobs still in place, they filter and play,
While the teams take a break, just for today.
Hopping along, we optimize our way! 🐇✨
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
What changes are proposed in this pull request?
We can add concurrency groups with
cancel-in-progress
to cancel pre-existing jobs. It seems like a good idea to save money on workflows that might take a bit on PRs.How is this patch tested? If it is not, please explain why.
This change was tested with GH Actions
Release Notes
Is this a user-facing change that should be mentioned in the release notes?
(Details in 1-2 sentences. You can just refer to another PR with a description if this PR is part of a larger change.)
What areas of FiftyOne does this PR affect?
fiftyone
Python library changesSummary by CodeRabbit
New Features
Chores