From 4e38a980a45549f0c37ed16fb1325ef23ef1bd5e Mon Sep 17 00:00:00 2001 From: Victor Martinez Date: Thu, 31 Aug 2023 15:51:18 +0200 Subject: [PATCH] update: what the CI does --- .github/workflows/README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/.github/workflows/README.md b/.github/workflows/README.md index 009ca1113..56f614eb6 100644 --- a/.github/workflows/README.md +++ b/.github/workflows/README.md @@ -12,6 +12,11 @@ The whole process should look like: `Checkout` -> `Lint` -> `Test` -> `Coverage` -> `Benchmark` -> `Release` +There are some other stages that run for every push on the main branches: + +* [Snapshoty](./snapshoty.yml) +* [Microbenchmark](./microbenchmark.yml) + ### Scenarios * Matrix compatibility runs on branches, tags and PRs basis. @@ -41,7 +46,6 @@ Every time there is a merge to main or any release branches the whole workflow w This process has been fully automated and it gets triggered when a tag release has been created, Continuous Deployment based, aka no input approval required. - ### OpenTelemetry There is a GitHub workflow in charge to populate what the workflow run in terms of jobs and steps. Those details can be seen in [here](https://ela.st/oblt-ci-cd-stats) (**NOTE**: only available for Elasticians).