Added hyperlink to Github (#316)

* Added hyperlink to Github * Update website/docs/docs/workshops/bi-directional/pre_requisites.md Co-authored-by: JP-Ellis <github@jpellis.me> * Improved final wording --------- Co-authored-by: JP-Ellis <github@jpellis.me>
pactflow · Jan 15, 2025 · 02ffeba · 02ffeba
1 parent 64cbb93
commit 02ffeba
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 1 deletion.
diff --git a/website/docs/docs/workshops/bi-directional/pre_requisites.md b/website/docs/docs/workshops/bi-directional/pre_requisites.md
@@ -15,4 +15,9 @@ These instructions have been written for, and tested, in a *bash* (not zsh) shel
 
 :::info
 If you have access to a second screen, we recommend that you use it for this workshop, as there is a lot of window switching involved.
-:::
+:::
+
+:::info
+We encourage you to follow the instructions in the workshop and try it yourself,
+but if you get stuck, you can checkout the code [here](https://github.com/pactflow/example-bi-directional-provider-dredd)
+:::
diff --git a/website/docs/docs/workshops/bi-directional/step5.md b/website/docs/docs/workshops/bi-directional/step5.md
@@ -48,6 +48,10 @@ This allows PactFlow to communicate to any future consumers of the provider, tha
 
 ## Deploy the provider to production via Github Actions
 
+In the real world, you typically do not deploy manually from local machine.
+Instead, you would have a CI/CD pipeline that would run the `can-i-deploy` command 
+and then deploy the provider to production, for example on a cloud provider of choice.
+
 ### Setup deployment environment
 
 :::info