Merge branch 'release/v19.10.0'

Author: dgibbs64

.gitattributes

@@ -19,4 +19,4 @@
 *.pdf  diff=astextplain
 *.PDF	 diff=astextplain
 *.rtf	 diff=astextplain
-*.RTF	 diff=astextplain
+*.RTF	 diff=astextplain

.github/ISSUE_TEMPLATE/new-server-request.md

@@ -26,4 +26,4 @@ If yes Use SteamDB to get the appid. (https://steamdb.info).
 We only support Linux servers and do not support Wine.
 
 * [ ] Yes
-* [ ] No
+* [ ] No

.github/potential-duplicates.yml

@@ -10,4 +10,4 @@ referenceComment: >
   Potential duplicates:
   {{#issues}}
     - [#{{ number }}] {{ title }} ({{ accuracy }}%)
-  {{/issues}}
+  {{/issues}}

.github/pull_request_template.md

@@ -19,26 +19,11 @@ PR will not be merged until all steps are complete.
 * [ ] This pull request links to an issue.
 * [ ] This pull request uses the `develop` branch as its base.
 * [ ] This code follows the style guidelines of this project.
-* [ ] I have provided Co-author details below.
 * [ ] I have performed a self-review of my own code.
 * [ ] I have checked that this code is commented where required.
 * [ ] I have provided a detailed enough description of this PR.
 * [ ] I have checked If documentation needs updating.
 
-## Provide Github Email
-
-Fill out below info or tick box below:
-```
-Co-authored-by: John Doe <[email protected]>
-```
-
-- [ ] I do not wish to provide an email. I am aware this will hide me as the author of this commit.
-
-All pull requests will now be squashed to create a tidy commit history and simplify changelog creation. You can provide either your own email or a GitHub-provided no-reply email.
-
-When a PR is squashed the author becomes the person who squashed the PR. This removes you as the author of your own PR.
-The only workaround for this is to add your details as a co-author. More info about co-authors can be found [here](https://help.github.com/en/articles/creating-a-commit-with-multiple-authors).
-
 ## Documentation
 
 If documentation does need updating either update it by creating a PR (preferred) or request a documentation update.

.github/request-info.yml

@@ -3,7 +3,7 @@
 # *Required* Comment to reply with
 requestInfoReplyComment: >
   ![More Data required](https://i.imgur.com/yS9cecv.png)
-  More data is required to assist with this issue 
+  More data is required to assist with this issue
   or issue template was not used correctly.
   https://linuxgsm.com/support/#guide
 
@@ -14,4 +14,4 @@ requestInfoReplyComment: >
 #  - updates
 
 # *OPTIONAL* Label to be added to Issues and Pull Requests with insufficient information given
-requestInfoLabelToAdd: "needs more info"
+requestInfoLabelToAdd: "needs more info"

.github/topissuebot.yml

@@ -1,4 +1,4 @@
 # Configuration for top-issue-bot
 labelName: ":thumbsup: Top Issue!"
 labelColor: "f442c2"
-numberOfIssuesToLabel: 5
+numberOfIssuesToLabel: 5

.github/welcome.yml

@@ -18,4 +18,4 @@ newPRWelcomeComment: >
 firstPRMergeComment: >
   Congratulations on merging your first pull request! Thank you for supporting LinuxGSM!
 
-# It is recommend to include as many gifs and emojis as possible
+# It is recommend to include as many gifs and emojis as possible

.github/write-good.yml

@@ -1,4 +1,4 @@
 # .github/write-good.yml
 writeGood: true
 alex: true
-spellchecker: true
+spellchecker: true

.gitignore

@@ -1,2 +1,2 @@
 *.db
-.idea
+.idea

CONTRIBUTING.md

@@ -33,4 +33,4 @@ This will help us in understanding your code and determining where problems may
 Start reading our code and you'll get the hang of it. Explore how functions are organized and you'll see how we strive for readable code.
 
 Please give the following document a read and adjust your code according to its specifications.
-[Syntax & Coding Conventions](https://github.com/GameServerManagers/LinuxGSM/wiki/Syntax-and-Conventions)
+[Syntax & Coding Conventions](https://github.com/GameServerManagers/LinuxGSM/wiki/Syntax-and-Conventions)