Skip to content

Commit 7f0e413

Browse files
committed
fix link to /issues to use internal/relative links within GH repo
1 parent 67009f4 commit 7f0e413

File tree

1 file changed

+6
-7
lines changed

1 file changed

+6
-7
lines changed

CONTRIBUTING.md

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,6 @@
55
For a new project, search-and-replace
66
- CURRENT_PROJECT
77
- COFC_URL (The URL for the code-of-conduct for the current project)
8-
- ISSUES_URL (The URL for the Issues board for the current project)
98
-->
109

1110
First off, thanks for taking the time to contribute! ❤️
@@ -55,15 +54,15 @@ unacceptable behavior to <MAINTAINER>.
5554
> documentation.
5655
5756
Before you ask a question, it is best to search for existing
58-
[Issues](ISSUES_URL) that might help you. In
57+
[Issues](/issues) that might help you. In
5958
case you have found a suitable issue and still need clarification, you can write
6059
your question in this issue. It is also advisable to search the internet for
6160
answers first.
6261

6362
If you then still feel the need to ask a question and need clarification, we
6463
recommend the following:
6564

66-
- Open an [Issue](ISSUES_URL/new).
65+
- Open an [Issue](/issues/new).
6766
- Provide as much context as you can about what you're running into.
6867
- Provide project and platform versions (nodejs, npm, etc), depending on what
6968
seems relevant.
@@ -111,7 +110,7 @@ steps in advance to help us fix any potential bug as fast as possible.
111110
- To see if other users have experienced (and potentially already solved) the
112111
same issue you are having, check if there is not already a bug report existing
113112
for your bug or error in the
114-
[bug tracker](ISSUES_URL?q=label%3Abug).
113+
[bug tracker](/issues?q=label%3Abug).
115114

116115
<!-- omit in toc -->
117116
#### How Do I Submit a Good Bug Report?
@@ -125,7 +124,7 @@ be sent encrypted as well. -->
125124
We use GitHub issues to track bugs and errors. If you run into an issue with the
126125
project:
127126

128-
- Open an [Issue](ISSUES_URL/new). (Since we
127+
- Open an [Issue](/issues/new). (Since we
129128
can't be sure at this point whether it is a bug or not, we ask you not to talk
130129
about a bug yet and not to label the issue.)
131130
- Explain the behavior you would expect and the actual behavior.
@@ -152,7 +151,7 @@ the community to understand your suggestion and find related suggestions.
152151
- Make sure that you are using the latest version.
153152
- Read the documentation carefully and find out if the functionality is already
154153
covered, maybe by an individual configuration.
155-
- Perform a [search](ISSUES_URL) to see if the
154+
- Perform a [search](/issues) to see if the
156155
enhancement has already been suggested. If it has, add a comment to the
157156
existing issue instead of opening a new one.
158157
- Find out whether your idea fits with the scope and aims of the project. It's
@@ -164,7 +163,7 @@ the community to understand your suggestion and find related suggestions.
164163
#### How Do I Submit a Good Enhancement Suggestion?
165164

166165
Enhancement suggestions are tracked as
167-
[GitHub issues](ISSUES_URL).
166+
[GitHub issues](/issues).
168167

169168
- Use a **clear and descriptive title** for the issue to identify the
170169
suggestion.

0 commit comments

Comments
 (0)