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
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ Before you ask a question, it is best to search for existing [Issues](https://gi
36
36
37
37
If you then still feel the need to ask a question and need clarification, we recommend the following:
38
38
39
-
- Open an [Issue](/issues/new).
39
+
- Open an [Issue](https://github.com/quicksilver-zone/quicksilver/issues/new/choose).
40
40
- Provide as much context as you can about what you're running into.
41
41
- Provide project and platform versions (os, arch, go, etc.), depending on what seems relevant.
42
42
@@ -58,7 +58,7 @@ A good bug report shouldn't leave others needing to chase you up for more inform
58
58
59
59
- Make sure that you are using the latest version.
60
60
- Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the [documentation](https://docs.quicksilver.zone). If you are looking for support, you might want to check [this section](#i-have-a-question)).
61
-
- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](issues?q=label%3Abug).
61
+
- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/quicksilver-zone/quicksilver/issues?q=label%3Abug).
62
62
- Collect information about the bug:
63
63
- Stack trace (Traceback)
64
64
- OS, Platform and Version (Windows, Linux, macOS, x86, ARM)
@@ -73,7 +73,7 @@ A good bug report shouldn't leave others needing to chase you up for more inform
73
73
74
74
We use GitHub issues to track bugs and errors. If you run into an issue with the project:
75
75
76
-
- Open an [Issue](/issues/new). (Since we can't be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.)
76
+
- Open an [Issue](https://github.com/quicksilver-zone/quicksilver/issues/new/choose). (Since we can't be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.)
77
77
- Explain the behavior you would expect and the actual behavior.
78
78
- Please provide as much context as possible and describe the *reproduction steps* that someone else can follow to recreate the issue on their own. This usually includes your code. For good bug reports you should isolate the problem and create a reduced test case.
79
79
- Provide the information you collected in the previous section.
@@ -94,13 +94,13 @@ This section guides you through submitting an enhancement suggestion for Quicksi
94
94
95
95
- Make sure that you are using the latest version.
96
96
- Read the [documentation](https://docs.quicksilver.zone) carefully and find out if the functionality is already covered, maybe by an individual configuration.
97
-
- Perform a [search](/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
97
+
- Perform a [search](https://github.com/quicksilver-zone/quicksilver/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
98
98
- Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on/plugin library.
99
99
100
100
<!-- omit in toc -->
101
101
#### How Do I Submit a Good Enhancement Suggestion?
102
102
103
-
Enhancement suggestions are tracked as [GitHub issues](/issues).
103
+
Enhancement suggestions are tracked as [GitHub issues](https://github.com/quicksilver-zone/quicksilver/issues).
104
104
105
105
- Use a **clear and descriptive title** for the issue to identify the suggestion.
106
106
- Provide a **step-by-step description of the suggested enhancement** in as many details as possible.
Copy file name to clipboardExpand all lines: x/mint/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,7 +48,7 @@ the following formula:
48
48
49
49
### Minter
50
50
51
-
The [`Minter`](]https://github.com/quicksilver-zone/quicksilver/blob/b95f0dce1df0769068b2962868b97fdc6151752d/x/mint/types/mint.pb.go#L31) is an abstraction for holding current rewards information.
51
+
The [`Minter`](https://github.com/quicksilver-zone/quicksilver/blob/b95f0dce1df0769068b2962868b97fdc6151752d/x/mint/types/mint.pb.go#L31) is an abstraction for holding current rewards information.
0 commit comments