Quentin G eab65f34f9 feat(ci): use concurrency.group to cancel previous jobs (#4795) ... As recommended on the repo of the action we were using https://github.com/styfle/cancel-workflow-action, we should use `concurrency.group` rather than a dedicated action. Here is a PR to use it on all our workflows		2024-04-04 09:30:55 +02:00
..
cd-deploy-main.yaml	feat(ci): automate CI tags and pass github context (#4652)	2024-03-26 09:01:39 +01:00
cd-deploy-tag.yaml	feat(ci): automate CI tags and pass github context (#4652)	2024-03-26 09:01:39 +01:00
ci-chromatic.yaml	feat(ci): use concurrency.group to cancel previous jobs (#4795)	2024-04-04 09:30:55 +02:00
ci-chrome-extension.yaml	feat(ci): use concurrency.group to cancel previous jobs (#4795)	2024-04-04 09:30:55 +02:00
ci-docs.yaml	feat(ci): use concurrency.group to cancel previous jobs (#4795)	2024-04-04 09:30:55 +02:00
ci-front.yaml	feat(ci): use concurrency.group to cancel previous jobs (#4795)	2024-04-04 09:30:55 +02:00
ci-server.yaml	feat(ci): use concurrency.group to cancel previous jobs (#4795)	2024-04-04 09:30:55 +02:00
ci-test-docker-compose.yaml	feat: init docker compose test (#4730)	2024-04-03 18:08:21 +02:00
ci-utils.yaml	feat(ci): use concurrency.group to cancel previous jobs (#4795)	2024-04-04 09:30:55 +02:00