Update the README to include the old repo name and bump release version

GitHooksToolbox · May 20, 2021 · b68da26 · b68da26
1 parent 3aed374
commit b68da26
Show file tree

Hide file tree

Showing 3 changed files with 15 additions and 5 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -5,13 +5,21 @@ All notable changes to this project will be documented in this file.
 
 This changelog was automatically generated using [Caretaker](https://github.com/DevelopersToolbox/caretaker) by [Wolf Software](https://github.com/WolfSoftware)
 
-### [Unreleased](https://github.com/GitToolbox/block-default-branch-commit/compare/v0.1.0...HEAD)
+### [v0.1.1](https://github.com/GitToolbox/block-default-branch-commit/compare/v0.1.0...v0.1.1)
 
-- Rename [`[head]`](https://github.com/GitToolbox/block-default-branch-commit/commit/)
+> Released on May, 20th 2021
+
+- Update the README to include the old repo name and bump release version [`[head]`](https://github.com/GitToolbox/block-default-branch-commit/commit/)
+
+- Rename [`[3aed374]`](https://github.com/GitToolbox/block-default-branch-commit/commit/3aed3745cb191023651f0ebb0fc11ecaccfbaf8d)
 
 - Added a method to dynamically calculate the default head branch [`[9ee0bc1]`](https://github.com/GitToolbox/block-default-branch-commit/commit/9ee0bc15b7f6806624cd972c78473ff586879612)
 
 - Add a new travis job to run github-linguist for information only [`[06cffa7]`](https://github.com/GitToolbox/block-default-branch-commit/commit/06cffa7ff84297b93506a5849021780c9ce44826)
 
+### [v0.1.0](https://github.com/GitToolbox/block-default-branch-commit/releases/v0.1.0)
+
+> Released on February, 10th 2021
+
 - The initial commit [`[b27d33a]`](https://github.com/GitToolbox/block-default-branch-commit/commit/b27d33aa68d1649edb6965ba5c81dd500df5e9f2)
 
diff --git a/README.md b/README.md
@@ -35,11 +35,13 @@
 	</a>
 </p>
 
+> This project was formally called ```block-master-branch``` but has been renamed to reflect the more dynamic nature of the solution.
+
 ## Overview
 
-No matter which style of git workflow you use, it is generally (but not by everyone) agreed that committing directly into the default branch is a bad idea.
+No matter which style of git workflow you use, it is generally (but not by everyone) agreed that committing directly into the ```default branch``` is a bad idea.
 
-> We use the term 'default branch' to mean any branch you have configured as your default, this is often 'master' or 'main' but can be configured on a repo by repo basis. 
+> We use the term ```default branch``` to mean any branch you have configured as your default, this is often ```master``` or ```main``` but can be configured on a repo by repo basis. 
 
 Some of the reasons for this include (and there are many many more):
 

diff --git a/VERSION.txt b/VERSION.txt
@@ -1 +1 @@
-0.1.0
+0.1.1