From 8b824a982ac5744cd50bef1df9cde54f59f8a839 Mon Sep 17 00:00:00 2001
From: Michael Stanclift <mstanclift@vmware.com>
Date: Thu, 28 May 2020 22:11:04 -0500
Subject: [PATCH 1/3] Update README.md

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 493c922..6c6f599 100644
--- a/README.md
+++ b/README.md
@@ -160,7 +160,7 @@ Before executing, this will make a copy of the remote database under `backup/gra
 This function purposefuly asks for user interaction to avoid being accidentally automated.
 
 ### The Restore Function
-Graviy Sync can also `restore` the database on the secondary Pi-hole in the event you've overwritten it accidentally. This might happen in the above scenario where you've had your primary Pi-hole down for an extended period, made changes to the secondary, but perhaps didn't get a chance to perform a `push` of the changes back to the primary, before your automated sync ran.
+Gravity Sync can also `restore` the database on the secondary Pi-hole in the event you've overwritten it accidentally. This might happen in the above scenario where you've had your primary Pi-hole down for an extended period, made changes to the secondary, but perhaps didn't get a chance to perform a `push` of the changes back to the primary, before your automated sync ran.
 
 ```bash
 ./gravity-sync.sh restore

From 4cb6370436760345c40c548d6ceffbf1619f7108 Mon Sep 17 00:00:00 2001
From: Michael Stanclift <mstanclift@vmware.com>
Date: Fri, 29 May 2020 21:16:42 -0500
Subject: [PATCH 2/3] Update gravity-sync.sh

---
 gravity-sync.sh | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gravity-sync.sh b/gravity-sync.sh
index 2d10018..16db2e0 100755
--- a/gravity-sync.sh
+++ b/gravity-sync.sh
@@ -896,7 +896,7 @@ function show_version {
 	MESSAGE="Running Version: ${GREEN}${VERSION}${NC}"
 	echo_info
 
-	GITVERSION=$(curl -sf https://raw.githubusercontent.com/vmstan/gravity-sync/development/VERSION)
+	GITVERSION=$(curl -sf https://raw.githubusercontent.com/vmstan/gravity-sync/master/VERSION)
 	if [ -z "$GITVERSION" ]
 	then
 		MESSAGE="Latest Version: ${RED}Unknown${NC}"
@@ -1192,4 +1192,4 @@ case $# in
 		echo_fail
 			list_gs_arguments
 	;;
-esac
\ No newline at end of file
+esac

From 8ec1c597045b79ec68603a41adbc05ae5af0ea18 Mon Sep 17 00:00:00 2001
From: Michael Stanclift <mstanclift@vmware.com>
Date: Mon, 1 Jun 2020 21:00:52 -0500
Subject: [PATCH 3/3] Update issue templates

---
 .github/ISSUE_TEMPLATE/bug_report.md      | 25 +++++++++++++++++++++++
 .github/ISSUE_TEMPLATE/feature_request.md | 20 ++++++++++++++++++
 2 files changed, 45 insertions(+)
 create mode 100644 .github/ISSUE_TEMPLATE/bug_report.md
 create mode 100644 .github/ISSUE_TEMPLATE/feature_request.md

diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
new file mode 100644
index 0000000..c8a003e
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -0,0 +1,25 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Configuration:**
+ - OS for Primary/Secondary: [e.g. Ubuntu/DietPi]
+ - Platform for Primary/Secondary: [e.g. VMware ESXi/Raspberry Pi 4]
+ - SSH Server/Client: [e.g. OpenSSH/Dropbear]
+ - SSH Authentication: [e.g. Keypair, Password]
+ - Gravity Sync Version: [e.g. 1.7.6]
+ - Pi-hole Versions: [e.g. v5.0]
+
+**Additional context**
+Add any other context about the problem here. If you have any advanced flags set in your `gravity-sync.conf` please list them here.
diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md
new file mode 100644
index 0000000..bbcbbe7
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.