(GH-1932) Add info, warning and danger callouts

Author: gep13

docs/input/docs/build-server-support/build-server/azure-devops.md

@@ -135,12 +135,16 @@ to configure.
 
 If GitVersion does not find any substitutions it will just default to using `FullSemVer`
 
-**IMPORTANT:** If you currently use `$(rev:.r)` in your build number, that won't
+:::{.alert .alert-danger}
+**Important**
+
+If you currently use `$(rev:.r)` in your build number, that won't
 work correctly if you
 use GitVersion variables as well due to the delayed expansion of the GitVersion
 vars. Instead, you might be able to use `$(GitVersion_BuildMetaData)` to achieve
 a similar result.  See [Variables](../../more-info/variables) for more info on the
 variables.
+:::
 
 #### Known limitations
 

docs/input/docs/build-server-support/build-server/myget.md

@@ -19,11 +19,15 @@ generated by GitVersion and apply this [MyGet Environment Variable](http://docs.
 wherever it is used during the build process.
 * Ensure the build script has been pushed to your source repository root. Done :)
 
-Note: If you require the `AssemblyInfo.cs` files in your project to be patched
+:::{.alert .alert-info}
+**Note**
+
+If you require the `AssemblyInfo.cs` files in your project to be patched
 with the information from GitVersion, you will have to run it manually, for
 example using the command:
 
 `call %GitVersion% /updateassemblyinfo true`.
+:::
 
 Also check [docs.myget.org](http://docs.myget.org/docs/reference/build-services#GitVersion_and_Semantic_Versioning)
 for the latest full info.

docs/input/docs/configuration.md

@@ -16,8 +16,12 @@ working directory. It can be the root repository directory or any subdirectory
 in case you have a single repository for more than one project or are restricted
 to commit into a subdirectory.
 
-**Note:** GitVersion ships with internal default configuration which works with
+:::{.alert .alert-info}
+**Note**
+
+GitVersion ships with internal default configuration which works with
 GitHubFlow and GitFlow, probably with others too.
+:::
 
 The *develop* branch is set to `ContinuousDeployment` mode by default as we have
 found that is generally what is needed when using GitFlow.
@@ -246,7 +250,11 @@ Custom merge message formats are evaluated _before_ any built in formats.
 
 Then we have branch specific configuration, which looks something like this:
 
-**NOTE: ** v4 changed from using regexes for keys, to named configs
+:::{.alert .alert-info}
+**Note**
+
+v4 changed from using regexes for keys, to named configs
+:::
 
 If you have branch specific configuration upgrading to v4 will force you to
 upgrade.

docs/input/docs/faq.md

@@ -41,9 +41,13 @@ way.
 So `1.0.1-rc.1+5` would become `1.0.1-rc0001`, this takes into account
 characters which are not allowed and NuGets crap sorting.
 
-**note: ** The `NuGetVersion` variable is floating, so when NuGet 3.0 comes out
+:::{.alert .alert-info}
+**Note**
+
+The `NuGetVersion` variable is floating, so when NuGet 3.0 comes out
 with proper SemVer support GitVersion will switch this variable to a proper
 SemVer.
+:::
 
 If you want to fix the version, use `NuGetVersionV2` which will stay the same
 after NuGet 3.0 comes out

docs/input/docs/reference/versioning-modes/mainline-development.md

@@ -43,11 +43,15 @@ Here is an example of what mainline development looks like:
 
 ![Mainline mode](../../img/mainline-mode.png)
 
-**WARNING:** This approach can slow down over time, we recommend to tag
+:::{.alert .alert-warning}
+**Warning**
+
+This approach can slow down over time, we recommend to tag
 intermittently (maybe for minor or major releases) because then GitVersion
 will start the version calculation from that point. Much like a snapshot in an
 event sourced system. We will probably add in warnings to tag when things are
 slowing down.
+:::
 
 ## Usage
 By default GitVersion is set up to do [Continuous Delivery](continuous-delivery)

docs/input/docs/usage/command-line.md

@@ -7,9 +7,13 @@ If you want a command line version installed on your machine then you can use
 [Chocolatey](http://chocolatey.org) or [Homebrew](https://brew.sh/) to install
 GitVersion.
 
-> **Hint**: While documentation and help use '/' as command prefix the hyphen '-'
+:::{.alert .alert-info}
+**Hint**
+
+While documentation and help use '/' as command prefix the hyphen '-'
 is supported as well and is a better alternative for usage on \*nix systems.
 Example: *-output json vs. /output json*
+:::
 
 ## Chocolatey
 

docs/input/docs/usage/gem.md

@@ -5,8 +5,12 @@ Title: Gem
 
 Just a gem wrapper around the command line to make it easier to consume from Rake.
 
-**NOTE** This is currently not being pushed.. Please get in touch if you are
-using this
+:::{.alert .alert-info}
+**Note**
+
+This is currently not being pushed. Please get in touch if you are
+using this.
+:::
 
 If you want a Ruby gem version installed on your machine then you can use
 [Bundler](http://bundler.io/) or [Gem](http://rubygems.org/) to install the
@@ -45,5 +49,9 @@ include GitVersion
 puts git_version('C:/read/info/from/another/repository').sha
 ```
 
-**Note:** Mono is not currently supported due to downstream dependencies on
+:::{.alert .alert-info}
+**Note**
+
+Mono is not currently supported due to downstream dependencies on
 libgit2. The Gem can only be used with the .NET framework
+:::

docs/input/docs/usage/nuget-library.md

@@ -5,7 +5,11 @@ Title: NuGet Library
 
 To use GitVersion from your own code.
 
-**Warning, we are not semantically versioning this library and it should be considered unstable.**
+:::{.alert .alert-warning}
+**Warning**
+
+We are not semantically versioning this library and it should be considered unstable.**
+:::
 
 It also is not currently documented. Please open an issue if you are consuming
 the library to let us know, and why you need to.