inclusion of the documentation folder

Author: JPrendy

documentations/gitEmptyCommitDocument.md

@@ -0,0 +1,15 @@
+# Git Empty Commit Documentation
+
+## Description
+
+The following documentation outlines how to send an empty commit to trigger various kinds of things in a repository.
+
+## Git Empty Commit
+
+So, if we want to send an empty commit, we want to have something like the following in the terminal.
+
+`git commit --allow-empty -m "Empty commit"`
+
+`git push`
+
+If you are still having issues, refer to the following documentation [link](https://coderwall.com/p/vkdekq/git-commit-allow-empty).

documentations/gitSquashDocument.md

@@ -0,0 +1,25 @@
+# Git Squash Documentation
+
+## Description
+
+The following documentation outlines how to Git Squash.
+
+## Git Squash Commits with Git Graph
+
+The following outlines how to Git Squash multiple commits easily in VS Code.
+
+So, let's say we want to Git Squash to the base branch of our pr, we take note of the commit number `69d81e38`
+
+<p><img src="../images/baseCommitInPr.png" width="800"/></p>
+
+So, we got to Git Graph in VS Code and then we look for that commit number and then go to one just before that and we want to do something like the following where we `reset` the current branch.
+
+<p><img src="../images/resetCurrentBranch.png" width="800"/></p>
+
+You want to click `Mixed` as the reset.
+
+<p><img src="../images/mixedReset.png" width="800"/></p>
+
+Once, that is reset, use `git add`, `git commit` and `git push` as normal and then you should see on Github that your branch has been squashed into one commit. 
+
+If you are still having issues, refer to the following documentation [link](https://dannyherran.com/2020/06/git-squash-commit-vs-code/#:~:text=Right%2Dclick%20the%20commit%20that,current%20branch%20to%20this%20commit%E2%80%A6%E2%80%9D).

documentations/gitWorktreeDocument.md

@@ -0,0 +1,29 @@
+# Git Worktree Documentation
+
+## Description
+
+The following documentation outlines how to use Git Worktree.
+
+## Git Worktree
+
+The following outlines how to `git worktree` that allows you look at another branches contents without needing to checkout to that branch. If you type `git worktree` in your terminal, you will see a list of commands you can use.
+
+So, let's say we want to look at the contents of a branch called `test/labels`. we would do the following of either
+
+1). `git worktree add worktreeBranch test/labels`
+
+This will add the contents of the branch to a folder called `worktreeBranch` to your current folder.
+
+or
+
+2). `git worktree add ../worktreeBranch test/labels`
+
+This will add the contents of the branch to a folder called `worktreeBranch` to your current folder but moved up by one directory. There may be cases this may be more useful as you can open this in a new window, which will make it easier to differentiate the two branches.
+
+To list your current worktree's, use the following command `git worktree list`.
+
+To remove any old worktrees you no longer need use the following command to git rid of the example we used, which was `worktreeBranch`.
+
+`git worktree remove worktreeBranch`. 
+
+If you are still having issues, refer to the following video [link](https://www.youtube.com/watch?v=cRunWRC8ye0).