Move proposal 2 to docs/proposals

cncf-tags · Jun 28, 2024 · 9649002 · 9649002
1 parent f38828b
commit 9649002
Show file tree

Hide file tree

Showing 5 changed files with 3 additions and 3 deletions.
diff --git a/.../docs/proposals/calling-benchmark-job.png → ...posals/diagrams/calling-benchmark-job.png b/.../docs/proposals/calling-benchmark-job.png → ...posals/diagrams/calling-benchmark-job.png
diff --git a/...als/green-reviews-pipeline-components.png → ...ams/green-reviews-pipeline-components.png b/...als/green-reviews-pipeline-components.png → ...ams/green-reviews-pipeline-components.png
diff --git a/...e/content/docs/proposals/pipeline-run.png → docs/proposals/diagrams/pipeline-run.png b/...e/content/docs/proposals/pipeline-run.png → docs/proposals/diagrams/pipeline-run.png
diff --git a/...oposals/files/trigger-deploy-pipeline.svg → ...sals/diagrams/trigger-deploy-pipeline.svg b/...oposals/files/trigger-deploy-pipeline.svg → ...sals/diagrams/trigger-deploy-pipeline.svg
diff --git a/...ontent/docs/proposals/proposal-002-run.md → docs/proposals/proposal-002-run.md b/...ontent/docs/proposals/proposal-002-run.md → docs/proposals/proposal-002-run.md
@@ -185,7 +185,7 @@ The Green Reviews automated pipeline relies on putting together different reusab
 
 There are different components defined here and shown in the following diagram.
 
-![Green Reviews pipeline components](green-reviews-pipeline-components.png "Green Reviews pipeline components")
+![Green Reviews pipeline components](diagrams/green-reviews-pipeline-components.png "Green Reviews pipeline components")
 
 1. **Green Reviews pipeline**: the Continuous Integration pipeline which deploys a CNCF project to a test cluster, runs a set of benchmarks while measuring carbon emissions and stores the results. It is implemented by the workflows listed below.
 2. **Cron workflow**: This refers to the initial GitHub Action workflow (described in proposal 1) and which dispatches a project workflow (see next definition).
@@ -205,7 +205,7 @@ As a Job that calls another GitHub Action workflow (yes, yet another workflow
 
 The two options for defining a benchmark test are illustrated below.
 
-![Calling the benchmark job](calling-benchmark-job.png "Calling the Benchmark job")
+![Calling the benchmark job](diagrams/calling-benchmark-job.png "Calling the Benchmark job")
 
 ### Running & Defining Benchmark Jobs
 
@@ -293,7 +293,7 @@ jobs:
 
 A Job can be fetched from other GitHub organizations and repositories using the `jobs.<job_id>.uses` syntax defined [here](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_iduses). This syntax can be configured to use `@main` or `@another-branch` which would be nice for versioning and testing specific releases.
 
-![Pipeline run](pipeline-run.png "An example pipeline run")
+![Pipeline run](diagrams/pipeline-run.png "An example pipeline run")