From 40ca351febfd2a6ae742574b289b3acbd80e8d93 Mon Sep 17 00:00:00 2001
From: Predrag Gruevski <2348618+obi1kenobi@users.noreply.github.com>
Date: Sun, 7 Aug 2022 22:10:06 -0400
Subject: [PATCH] Mark the README code blocks as YAML.

---
 README.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 50f386e..fc30a70 100644
--- a/README.md
+++ b/README.md
@@ -6,7 +6,7 @@ By default, this action assumes that:
 - Your releases are tagged in git as `v{major}.{minor}.{patch}`, for example `v1.2.3`.
 
 Single-crate workspaces can use it as:
-```
+```yaml
 - name: Check semver
   uses: obi1kenobi/cargo-semver-checks-action@v1
 - name: Publish to crates.io
@@ -18,7 +18,7 @@ In a workspace with more than one crate:
 - use the `version-tag-prefix` setting to override the default prefix `v` to match the way the releases of your crate are tagged. The version number `1.2.3` will be appended to this prefix.
 
 For example, this is publishing `my-crate` whose releases are tagged as `my-crate-v1.2.3`:
-```
+```yaml
 - name: Check semver
   uses: obi1kenobi/cargo-semver-checks-action@v1
   with:
@@ -29,7 +29,7 @@ For example, this is publishing `my-crate` whose releases are tagged as `my-crat
 ```
 
 To check a different (non-library) target in a crate, use the `crate-target` setting:
-```
+```yaml
 - name: Check semver for my_binary
   uses: obi1kenobi/cargo-semver-checks-action@v1
   with: