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
If you want to ask a question, we assume that you have read the available link:https://pillars.dev[Documentation].
45
45
46
-
Before you ask a question, it is best to search for existing link:https://github.com/rlemaitre/pillars/issues[Issues] that might help you.
46
+
Before you ask a question, it is best to search for existing link:https://github.com/FunktionalIO/pillars/issues[Issues] that might help you.
47
47
In case you have found a suitable issue and still need clarification, you can write your question in this issue.
48
48
It is also advisable to search the internet for answers first.
49
49
50
50
If you then still feel the need to ask a question and need clarification, we recommend the following:
51
51
52
-
* Open an https://github.com/rlemaitre/pillars/issues/new[Issue].
52
+
* Open an https://github.com/FunktionalIO/pillars/issues/new[Issue].
53
53
* Provide as much context as you can about what you're running into.
54
54
* Provide project and platform versions (scala, sbt, etc), depending on what seems relevant.
55
55
@@ -70,7 +70,7 @@ Please complete the following steps in advance to help us fix any potential bug
70
70
71
71
* Make sure that you are using the latest version.
72
72
* 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 link:https://pillars.dev[documentation]. If you are looking for support, you might want to check <<i-have-a-question, this section>>.
73
-
* 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 link:https://github.com/rlemaitre/pillarsissues?q=label%3Abug[bug tracker].
73
+
* 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 link:https://github.com/FunktionalIO/pillars/issues?q=label%3Abug[bug tracker].
74
74
* Also make sure to search the internet (including Stack Overflow) to see if users outside of the GitHub community have discussed the issue.
75
75
* Collect information about the bug:
76
76
* Stack trace (Traceback)
@@ -88,7 +88,7 @@ Instead, sensitive bugs must be sent by email to mailto:[email protected][].
88
88
We use GitHub issues to track bugs and errors.
89
89
If you run into an issue with the project:
90
90
91
-
* Open an link:https://github.com/rlemaitre/pillars/issues/new[Issue].
91
+
* Open an link:https://github.com/FunktionalIO/pillars/issues/new[Issue].
92
92
(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.)
93
93
* Explain the behavior you would expect and the actual behavior.
94
94
* Please provide as much context as possible and describe the *reproduction steps* that someone else can follow to recreate the issue on their own.
@@ -114,7 +114,7 @@ Following these guidelines will help maintainers and the community to understand
114
114
115
115
* Make sure that you are using the latest version.
116
116
* Read the link:https://pillars.pillars.dev[documentation] carefully and find out if the functionality is already covered, maybe by an individual configuration.
117
-
* Perform a link:https://github.com/rlemaitre/pillars/issues[search] to see if the enhancement has already been suggested.
117
+
* Perform a link:https://github.com/FunktionalIO/pillars/issues[search] to see if the enhancement has already been suggested.
118
118
If it has, add a comment to the existing issue instead of opening a new one.
119
119
* Find out whether your idea fits with the scope and aims of the project.
120
120
It's up to you to make a strong case to convince the project's developers of the merits of this feature.
@@ -123,7 +123,7 @@ If you're just targeting a minority of users, consider writing an add-on/plugin
123
123
124
124
===== How Do I Submit a Good Enhancement Suggestion?
125
125
126
-
Enhancement suggestions are tracked as link:https://github.com/rlemaitre/pillars/issues[GitHub issues].
126
+
Enhancement suggestions are tracked as link:https://github.com/FunktionalIO/pillars/issues[GitHub issues].
127
127
128
128
* Use a *clear and descriptive title* for the issue to identify the suggestion.
129
129
* Provide a *step-by-step description of the suggested enhancement* in as many details as possible.
0 commit comments