From 12a6b35dcd8e81f11bc69ebd95d48ecb7123ab3e Mon Sep 17 00:00:00 2001 From: montgolfiere Date: Mon, 20 Apr 2020 21:20:24 +0100 Subject: [PATCH] Minor updates to README.md --- docs/build-and-release.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/build-and-release.md b/docs/build-and-release.md index b9466530..cbc6f14f 100644 --- a/docs/build-and-release.md +++ b/docs/build-and-release.md @@ -19,6 +19,8 @@ Travis CI builds differ by branch: > - alfresco/alfresco-imagemagick > - alfresco/alfresco-tika > - alfresco/alfresco-libreoffice + > - alfresco/alfresco-transform-misc + > - alfresco/alfresco-transform-core-aio - if the commit message contains the `[trigger release]` tag, the builds will also include the _Release_ stage; - PR builds where the latest commit contains the `[trigger release]` tag will execute dry runs @@ -51,7 +53,7 @@ maven command, i.e. 4. Create a new commit with the `[trigger release]` tag in its message. If no local changes have been generated by steps (2) and (3), then an empty commit should be created - e.g. ```bash - git commit --allow-empty -m "ATS-###: Release AIS #.##.# [trigger release]" + git commit --allow-empty -m "ATS-###: Release T-Core (T-Engines) #.##.# [trigger release]" ``` > The location of the `[trigger release]` tag in the commit message is irrelevant.