From f07795c7007f0b7da49cae566cb12fba12f779d2 Mon Sep 17 00:00:00 2001
From: Excavator Bot <33266368+svc-excavator-bot@users.noreply.github.com>
Date: Fri, 22 Nov 2019 14:16:11 +0000
Subject: [PATCH] Excavator: Render CircleCI file using template specified in
 .circleci/template.sh (#297)

* Excavator: Render CircleCI file using template specified in .circleci/template.sh

* fix
---
 .circleci/config.yml | 3 +++
 README.md            | 2 +-
 2 files changed, 4 insertions(+), 1 deletion(-)

diff --git a/.circleci/config.yml b/.circleci/config.yml
index eaff16fee..45f583ba4 100644
--- a/.circleci/config.yml
+++ b/.circleci/config.yml
@@ -215,6 +215,9 @@ workflows:
           requires: [ compile ]
           filters: { tags: { only: /.*/ } }
 
+      - markdown:
+          filters: { tags: { only: /.*/ } }
+
       - trial-publish:
           requires: [ compile ]
 
diff --git a/README.md b/README.md
index 4c112dfee..84c4a77f6 100644
--- a/README.md
+++ b/README.md
@@ -136,7 +136,7 @@ Accessing services in containers from outside a container
 
 In tests it is likely services inside containers will need to be accessed in order to assert that they are behaving correctly. In addition, when tests run on Mac the Docker containers will be inside a Virtual Box machine and so must be accessed on an external IP address rather than the loopback interface.
 
-It is recommended to only specify internal ports in the `docker-compose.yml` as described in the [https://docs.docker.com/compose/compose-file/#ports](reference). This makes tests independent of the environment on the host machine and of each other.  Docker will then randomly allocate an external port. For example:
+It is recommended to only specify internal ports in the `docker-compose.yml` as described in the (reference)[https://docs.docker.com/compose/compose-file/#ports]. This makes tests independent of the environment on the host machine and of each other.  Docker will then randomly allocate an external port. For example:
 
 ```yaml
 postgres: