You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"comment": "The following entries disable rules that may conflict with Prettier see https://github.com/DavidAnson/markdownlint/blob/v0.34.0/style/prettier.json",
-[Issue and Pull Request Labels](#issue-and-pull-request-labels)
36
37
37
38
## Code of Conduct
38
39
@@ -44,7 +45,7 @@ This project and everyone participating in it is governed by the [LinuxGSM Code
44
45
45
46
This section guides you through submitting a bug report for LinuxGSM. Following these guidelines help maintainers and the community understand your report 📝, reproduce the behaviour💻, and find any related reports 🔎.
46
47
47
-
Before creating bug reports, please check [this list](https://github.com/GameServerManagers/linuxgsm/blob/master/CONTRIBUTING.md#before-submitting-a-bug-report) as you might find out that you don’t need to create one. When you are creating a bug report, please [include as many details as possible](https://github.com/GameServerManagers/linuxgsm/blob/master/CONTRIBUTING.md#how-do-i-submit-a-good-bug-report). Fill out [the required template](<[https://github.com/GameServerManagers/LinuxGSM/issues/new/choose](https://github.com/GameServerManagers/LinuxGSM/issues/new/choose)>), the information it asks for helps us resolve issues faster.
48
+
Before creating bug reports, please check [this list](https://github.com/GameServerManagers/linuxgsm/blob/master/CONTRIBUTING.md#before-submitting-a-bug-report) as you might find out that you don't need to create one. When you are creating a bug report, please [include as many details as possible](https://github.com/GameServerManagers/linuxgsm/blob/master/CONTRIBUTING.md#how-do-i-submit-a-good-bug-report). Fill out [the required template](<[https://github.com/GameServerManagers/LinuxGSM/issues/new/choose](https://github.com/GameServerManagers/LinuxGSM/issues/new/choose)>), the information it asks for helps us resolve issues faster.
48
49
49
50
#### Before Submitting A Bug Report
50
51
@@ -69,7 +70,7 @@ This section guides you through submitting a feature suggestion for LinuxGSM, in
69
70
70
71
#### Before Submitting An Feature Suggestion
71
72
72
-
-**Check the**[**documentation**](<https://docs.linuxgsm.com/%5D(https://docs.linuxgsm.com/)>) to confirm that the enhancement doesn’t already exist.
73
+
-**Check the**[**documentation**](<https://docs.linuxgsm.com/%5D(https://docs.linuxgsm.com/)>) to confirm that the enhancement doesn't already exist.
73
74
-**Check your**[**LinuxGSM version**](https://docs.linuxgsm.com/commands/update-lgsm)**.** A newer version of LinuxGSM may already have your enhancement.
74
75
-**Perform a**[**cursory search**](https://github.com/search?q=org:GameServerManagers%20type:issues&type=Issues) to see if the enhancement has already been suggested. If it has **and the enhancement is still open**, add a comment to the existing issue and give it a thumbs up instead of opening a new one.
75
76
@@ -122,7 +123,7 @@ The process described here has several goals:
122
123
Please follow these steps to have your contribution considered by the maintainers:
123
124
124
125
1. Follow all check-list in [the template](https://github.com/GameServerManagers/LinuxGSM/blob/master/.github/pull_request_template.md)
125
-
2. Follow the [style guides](#styleguides)
126
+
2. Follow the [style guides](#🍷 Styleguides)
126
127
3. After you submit your pull request, verify that all [status checks](https://help.github.com/articles/about-status-checks/) are passing
127
128
128
129
What if the status checks are failing? If a status check is failing, and you believe that the failure is unrelated to your change, please leave a comment on the pull request explaining why you believe the failure is unrelated. A maintainer will re-run the status check for you. If we conclude that the failure was a false positive, then we will open an issue to track that problem with our status check suite.
@@ -145,7 +146,7 @@ For example:
145
146
- If applied, this commit will **release version 1.0.0**
146
147
- If applied, this commit will **merge pull request #123 from user/branch**
147
148
148
-
Notice how this doesn’t work for the other non-imperative forms:
149
+
Notice how this doesn't work for the other non-imperative forms:
149
150
150
151
- If applied, this commit will **fixed bug with Y**
151
152
- If applied, this commit will **change the behaviour of X**
@@ -154,9 +155,9 @@ Notice how this doesn’t work for the other non-imperative forms:
154
155
155
156
Below is an example of the subject line for a pull request:
0 commit comments