🛠️ DevOps Tips 🛠️ If

🛠️ DevOps Tips 🛠️ If your GitHub workflows or jobs are failing due to jobs concurrently accessing and/or modifying shared resources, You can control execution at the workflow or job levels using the concurrency.

Jobs/Workflows in the same are prohibited from running at the same time, and you can cancel any jobs/workflow if you trigger another one.

Groups let you define compartments in which you don't want concurrent workflows running. They can be organized however you like. I find that using them in separate environments is a great practice.

Cancel-in-progress: specifies if the old running job/workflow needs to shut down.

Read more in docs: https://docs.github.com/en/actions/how-tos/write-workflows/choose-when-workflows-run/control-workflow-concurrency