From 27b467162b99f7a7890a9be9dc3a6d869fe2c0a3 Mon Sep 17 00:00:00 2001 From: Freddy Kristiansen Date: Wed, 15 Nov 2023 10:56:27 +0100 Subject: [PATCH] Nomenclature (#821) Fixes #820 --------- Co-authored-by: freddydk --- Workshop/PublishToProduction.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/Workshop/PublishToProduction.md b/Workshop/PublishToProduction.md index 3ed7be949..96ea64bf7 100644 --- a/Workshop/PublishToProduction.md +++ b/Workshop/PublishToProduction.md @@ -12,12 +12,20 @@ Then that environment will not be picked up for **continuous deployment**, but c Publish to the production environment by running the workflow and specifying which version to deploy, and which environment to deploy to. -**Note** that the default version is "current" - this will deploy the **release** with the name "current". If you want to just use the latest *build*, you would specify "latest": +**Note** that the default version is "current". This will deploy the **current release**. If you specify *latest* you will get the **latest build** + +> Current is the **current release**, which is the release tagged with *Latest* in your repository +> +> ![image](https://github.com/microsoft/AL-Go/assets/10775043/236f1eac-3045-4b19-90a1-1f81e2ad26a6) + +And... again, if you want to just use the latest *build*, you would specify "latest": | ![image](https://user-images.githubusercontent.com/10775043/232312134-0028a08d-1004-43f2-8127-aeeee8ed1a5e.png) | |-| But... - would you do that without running automated tests? +So... - let's look at adding some tests. + --- [Index](Index.md)  [next](AutomatedTests.md)