From 004756f006bedb12422adc5f88c10fc675ffcb90 Mon Sep 17 00:00:00 2001 From: Begona Guereca Date: Fri, 16 Sep 2022 13:54:58 -0700 Subject: [PATCH] Updated order so forecast is 3rd --- travis/2-audit.md | 2 +- travis/{6-forecast.md => 3-forecast.md} | 4 ++-- travis/{3-dry-run.md => 4-dry-run.md} | 2 +- travis/{4-custom-transformers.md => 5-custom-transformers.md} | 0 travis/{5-migrate.md => 6-migrate.md} | 4 ++-- 5 files changed, 6 insertions(+), 6 deletions(-) rename travis/{6-forecast.md => 3-forecast.md} (97%) rename travis/{3-dry-run.md => 4-dry-run.md} (98%) rename travis/{4-custom-transformers.md => 5-custom-transformers.md} (100%) rename travis/{5-migrate.md => 6-migrate.md} (96%) diff --git a/travis/2-audit.md b/travis/2-audit.md index a6a731d..39a0dbf 100644 --- a/travis/2-audit.md +++ b/travis/2-audit.md @@ -318,4 +318,4 @@ Each pipeline will have a variety of files written that include: ### Next lab -[Perform a dry-run of a Travis CI pipeline](3-dry-run.md) +[Forecast potential build runner usage](3-forecast.md) diff --git a/travis/6-forecast.md b/travis/3-forecast.md similarity index 97% rename from travis/6-forecast.md rename to travis/3-forecast.md index 66bcd30..88019f9 100644 --- a/travis/6-forecast.md +++ b/travis/3-forecast.md @@ -95,6 +95,6 @@ gh valet forecast --source-file-path tmp/**/jobs/*.json -o tmp/combined-forecast You can now inspect the output of the command to see a forecast report using all of the files matching the `tmp/**/jobs/*.json` pattern. -## Next steps +### Next Lab -This concludes all labs for migrating Travis CI pipelines to Actions with Valet! +[Perform a dry-run of a Travis CI pipeline](4-dry-run.md) diff --git a/travis/3-dry-run.md b/travis/4-dry-run.md similarity index 98% rename from travis/3-dry-run.md rename to travis/4-dry-run.md index a7ad1ff..ffebaa3 100644 --- a/travis/3-dry-run.md +++ b/travis/4-dry-run.md @@ -116,4 +116,4 @@ Despite these two pipelines using different syntax they will function equivalent ## Next lab -[Use custom transformers to customize Valet's behavior](./4-custom-transformers.md) +[Use custom transformers to customize Valet's behavior](./5-custom-transformers.md) diff --git a/travis/4-custom-transformers.md b/travis/5-custom-transformers.md similarity index 100% rename from travis/4-custom-transformers.md rename to travis/5-custom-transformers.md diff --git a/travis/5-migrate.md b/travis/6-migrate.md similarity index 96% rename from travis/5-migrate.md rename to travis/6-migrate.md index 23abccc..15f9aa6 100644 --- a/travis/5-migrate.md +++ b/travis/6-migrate.md @@ -46,6 +46,6 @@ Finally, you can merge the pull request once your review has completed. You can At this point, the migration has completed and you have successfully migrated a Travis CI pipeline to Actions! -### Next Lab +## Next steps -[Forecast potential build runner usage](6-forecast.md) +This concludes all labs for migrating Travis CI pipelines to Actions with Valet!