📝🎨 Adding Wiki link to top & emoji's to the headers PR (#12)

* 💡 Moved comments on error codes to wiki

* 📝 updated pipeline console log after logic checks added

* 🔖 marking version 1.0.1 after enhancements

The changes were not breaking to anything useing v1.0.0 commands.
This update only improves effiency

* 📝 added link to wiki page on argument value explination and fixed broken img links

* 📝 Changed capital formating for Wiki

* 📝🎨 Adding emoji's to the headers of the README file

✏️ Also addressed a missing word at the bottom talking about the kanban board

Author: devnetkc

README.md

@@ -2,6 +2,7 @@
 
 **Creator:** Ryan Valizan -- [@devnetkc](https://github.com/devnetkc)  
 **Latest Release:** [v1.0.1](https://github.com/devnetkc/wordpress-ssh-git-ci/releases/tag/v1.0.1)  
+**Wiki:** [How To Use](https://github.com/devnetkc/wordpress-ssh-git-ci/wiki)  
 **Tags:** git, WordPress, Bash, ci, Azure Azure DevOps, SiteGround, SSH, Azure Pipeline  
 **License:** GPLv3  
 **License URI:** [https://www.gnu.org/licenses/gpl-3.0.en.html](https://www.gnu.org/licenses/gpl-3.0.en.html)  
@@ -14,11 +15,13 @@ If there's SSH & Git, you can sync WordPress and Azure DevOps using git.
 
 Let your CI Pipeline manage getting those plugin updates from your unix WordPress server.  
 
-#### Live WordPress Branch History
+If you like the project, don't forget to click the ⭐up top!
+
+#### 🔴 Live WordPress Branch History
 
 ![AzureHistory](https://raw.githubusercontent.com/devnetkc/readme-assets/master/Images/WordPress-commit-history.png)
 
-### How To Use
+### 💻 How To Use
 
 ````cmd
 bash ~/wp-git-sync.sh \
@@ -30,9 +33,9 @@ bash ~/wp-git-sync.sh \
   -u $(DevOpsTokenUser)
 ````
 
-More information on the [arguments](https://github.com/devnetkc/wordpress-ssh-git-ci/wiki/How-To-Use#arguments) is available on the [WIKI](https://github.com/devnetkc/wordpress-ssh-git-ci/wiki) page [__How to Use__](https://github.com/devnetkc/wordpress-ssh-git-ci/wiki/How-To-Use)
+More information on the [arguments](https://github.com/devnetkc/wordpress-ssh-git-ci/wiki/How-To-Use#arguments) is available on the [Wiki](https://github.com/devnetkc/wordpress-ssh-git-ci/wiki) page [__How to Use__](https://github.com/devnetkc/wordpress-ssh-git-ci/wiki/How-To-Use)
 
-#### Azure Pipeline
+#### 🔧Azure Pipeline
 
 YAML Example:  
 *note: This example uses Azure Key store variables*
@@ -61,27 +64,27 @@ Console Log:
 ![WordPress-SSH-Git-CI](https://user-images.githubusercontent.com/26221344/91645717-0eae4d80-ea0d-11ea-81d9-b1e072766767.png)
 
 <!-- markdownlint-disable -->
-#### Requirements:
+#### 🔲Requirements:
 <!-- markdownlint-restore -->
 
-- **Web server have git capability** -- think this is the most important one
-- A method to store your secrete variables such as
+- [ ] **Web server have git capability** -- think this is the most important one
+- [ ] A method to store your secrete variables such as
   - username
   - password/token
-- SSH access to execute scripts on WordPress server
+- [ ] SSH access to execute scripts on WordPress server
   - *note: `cron` can serve as a slower alternative to SSH*
-- Some kind of CI pipeline or `cron` job to hook into after a branch update event triggers an agent to run the script remotely
+- [ ] Some kind of ci pipeline or `cron` job to hook into after a branch update event triggers an agent to run the script remotely
 
 <!-- markdownlint-disable -->
-#### What it has:
+#### 🚘What it has:
 <!-- markdownlint-restore -->
 
 - Parameter options for dynamic use
 - Separated functions
 - Is executed through an ssh call to your WordPress web server
 
 <!-- markdownlint-disable -->
-#### What it does is:
+#### 🚗 What it does is:
 <!-- markdownlint-restore -->
 
 - Check a git repo on a WordPress web server for changes
@@ -96,25 +99,25 @@ Console Log:
 
 Essentially, it allows WordPress developers to be more hands off with their shared hosting WordPress server backends, while still fully benefitting from any of the many source control repository and project board sites for git — but while using WordPress at the same time.
 
-## Contributing
+## 📈 Contributing
 
 Contrabutions are welcome!
 
-### Getting Started
+### 📚 Getting Started
 
-#### [Kanban Roadmap Board](https://github.com/devnetkc/wordpress-ssh-git-ci/projects/1)
+#### 📌 [Kanban Roadmap Board](https://github.com/devnetkc/wordpress-ssh-git-ci/projects/1)
 
 This is a simple script project to automate a painful manual process I dealt with every day at the office. This gets a WordPress git repository on a unix server and Azure DevOps to play nice with one another.
 
 If you see some adjustments to make, by all means suggest them.  This needs some clean up and refactoring yet.
 
 New issues or requests will be tracked on the [kanban board](https://github.com/devnetkc/wordpress-ssh-git-ci/projects/1) for the project.
 
-#### Emoji's in commits
+#### :bowtie: Emoji's in commits
 
 Emoji guide can be found here on the [gimoji project site](https://gitmoji.carloscuesta.me/).  Choose an emoji from the list provided above that fitst the fix or change you are submitting
 
-#### Submitting a pull request
+#### :twisted_rightwards_arrows: Submitting a pull request
 
 1) Fork the repository [wordpress-ssh-git-ci](https://github.com/devnetkc/wordpress-ssh-git-ci)
 2) Create a new branch off of [master](https://github.com/devnetkc/wordpress-ssh-git-ci/tree/master)
@@ -126,8 +129,10 @@ Emoji guide can be found here on the [gimoji project site](https://gitmoji.carlo
 
 It is also recommended to keep your pull request down to one specific issue or feature at a time.
 
-## WIKI & FAQ
+## ❓ Wiki & FAQ
 
-A [WIKI](https://github.com/devnetkc/wordpress-ssh-git-ci/wiki/) is available for the project and is moderatly managed.
+A [Wiki](https://github.com/devnetkc/wordpress-ssh-git-ci/wiki/) is available for the project and is moderatly managed.
 
 [FAQ information](https://github.com/devnetkc/wordpress-ssh-git-ci/wiki/FAQ) can be found [here](https://github.com/devnetkc/wordpress-ssh-git-ci/wiki/FAQ).
+
+The [Kanban Roadmap Board](https://github.com/devnetkc/wordpress-ssh-git-ci/projects/1) is also available to track progress or see tasks in querie to be worked on.