Reorder gitlab labs

gitlab/2-audit.md

@@ -180,4 +180,4 @@ Each pipeline will have a variety of files written that include:
 
 ### Next lab
 
-[Perform a dry-run migration of a GitLab pipeline](3-dry-run.md)
+[Forecast potential build runner usage](3-forecast.md)

gitlab/3-forecast.md

@@ -99,4 +99,4 @@ You can now inspect the output of the command to see a forecast report using all
 
 ## Next steps
 
-This concludes all labs for migrating GitLab pipelines to Actions with Valet!
+[Perform a dry-run migration of a GitLab pipeline](4-dry-run.md)

gitlab/4-dry-run.md

@@ -251,4 +251,4 @@ As an added challenge, try constructing and running the `dry-run` command yourse
 
 ## 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)

gitlab/5-custom-transformers.md

@@ -163,4 +163,4 @@ That's it! Congratulations, you have overridden Valet's default behavior by cust
 
 ## Next lab
 
-[Perform a production migration of a GitLab pipeline](5-migrate.md)
+[Perform a production migration of a GitLab pipeline](6-migrate.md)

gitlab/6-migrate.md

@@ -50,4 +50,4 @@ At this point, the migration has completed and you have successfully migrated a
 
 ### Next Lab
 
-[Forecast potential build runner usage](6-forecast.md)
+This concludes all labs for migrating GitLab pipelines to Actions with Valet!