format html after the docs are generated before pushing

Author: arturcic

build/Directory.Packages.props

@@ -13,6 +13,7 @@
     <PackageVersion Include="Cake.DotNetLocalTools.Module" Version="3.0.12" />
     <PackageVersion Include="Cake.Docker" Version="1.3.0" />
     <PackageVersion Include="Cake.Json" Version="7.0.1" />
+    <PackageVersion Include="Cake.Npx" Version="1.7.0" />
     <PackageVersion Include="Cake.Wyam" Version="2.2.14" />
     <PackageVersion Include="xunit.assert" Version="2.9.0" />
   </ItemGroup>

build/docs/Tasks/PublishDocs.cs

@@ -1,4 +1,5 @@
 using Cake.Git;
+using Cake.Npx;
 using Cake.Wyam;
 using Common.Utilities;
 
@@ -80,6 +81,7 @@ private static void PublishDocumentation(BuildContext context)
             context.WyamSettings.OutputPath = publishFolder;
             context.WyamSettings.NoClean = true;
             context.Wyam(context.WyamSettings);
+            context.Npx("prettier", arguments: "--write **/*.html", configureSettings: settings => settings.WorkingDirectory = publishFolder);
         }
 
         var schemaTargetDir = publishFolder.Combine("schemas");

build/docs/docs.csproj

@@ -8,6 +8,7 @@
     </ItemGroup>
     <ItemGroup>
         <PackageReference Include="Cake.Frosting.Git" />
+        <PackageReference Include="Cake.Npx" />
         <PackageReference Include="Cake.Wyam" />
     </ItemGroup>
 </Project>

docs/input/docs/learn/branching-strategies/githubflow/index.md

@@ -15,7 +15,7 @@ GitHubFlow is in a nutshell:
 2. Create a feature branch `git checkout -b myFeatureBranch`
 3. Do the feature/work
 4. Push feature branch to [origin](/docs/learn/git-setup#origin)
-5. Create pull request from origin/<featureBranch> -> upstream/main
+5. Create pull request from origin/{featureBranch} -> upstream/main
 6. Review, fix raised comments, merge your PR or even better, get someone else to.
 
 The main rule of GitHub Flow is that main should _always_ be deployable.