@@ -34,14 +34,14 @@ the experience for all involved. The community looks forward to your contributio
3434> available [ Documentation] ( https://superblockify.city/ ) .
3535
3636Before you ask a question, it is best to search for
37- existing [ Issues] ( https://github.com/NERDSITU /superblockify/issues ) that might help you.
37+ existing [ Issues] ( https://github.com/BikeNetKit /superblockify/issues ) that might help you.
3838In case you have found a suitable issue and still need clarification, you can write your
3939question in this issue. It is also advisable to search the internet for answers first.
4040
4141If you then still feel the need to ask a question and need clarification, we recommend
4242the following:
4343
44- - Open an [ Issue] ( https://github.com/NERDSITU /superblockify/issues/new ) .
44+ - Open an [ Issue] ( https://github.com/BikeNetKit /superblockify/issues/new ) .
4545- Provide as much context as you can about what you're running into.
4646- Provide project and platform versions (operating system, ` pip list ` ), depending on
4747 what seems relevant.
@@ -74,7 +74,7 @@ us fix any potential bug as fast as possible.
7474- To see if other users have experienced (and potentially already solved) the same issue
7575 you are having, check if there is not already a bug report existing for your bug or
7676 error in
77- the [ bug tracker] ( https://github.com/NERDSITU /superblockify/issues?q=label%3Abug ) .
77+ the [ bug tracker] ( https://github.com/BikeNetKit /superblockify/issues?q=label%3Abug ) .
7878- Also make sure to search the internet (including Stack Overflow) to see if users
7979 outside of the GitHub community have discussed the issue.
8080- Collect information about the bug:
@@ -93,7 +93,7 @@ us fix any potential bug as fast as possible.
9393We use GitHub issues to track bugs and errors. If you run into an issue with the
9494project:
9595
96- - Open an [ Issue] ( https://github.com/NERDSITU /superblockify/issues/new ) . (Since we can't
96+ - Open an [ Issue] ( https://github.com/BikeNetKit /superblockify/issues/new ) . (Since we can't
9797 be sure at this point whether it is a bug or not, we ask you not to talk about a bug
9898 yet and not to label the issue.)
9999- Explain the behavior you would expect and the actual behavior.
@@ -128,7 +128,7 @@ suggestion and find related suggestions.
128128- Make sure that you are using the latest version.
129129- Read the [ documentation] ( https://superblockify.city/ ) carefully and find out if the
130130 functionality is already covered, maybe by an individual configuration.
131- - Perform a [ search] ( https://github.com/NERDSITU /superblockify/issues ) to see if the
131+ - Perform a [ search] ( https://github.com/BikeNetKit /superblockify/issues ) to see if the
132132 enhancement has already been suggested. If it has, add a comment to the existing issue
133133 instead of opening a new one.
134134- Find out whether your idea fits with the scope and aims of the project. It's up to you
@@ -142,7 +142,7 @@ suggestion and find related suggestions.
142142#### How Do I Submit a Good Enhancement Suggestion?
143143
144144Enhancement suggestions are tracked
145- as [ GitHub issues] ( https://github.com/NERDSITU /superblockify/issues ) .
145+ as [ GitHub issues] ( https://github.com/BikeNetKit /superblockify/issues ) .
146146
147147- Use a ** clear and descriptive title** for the issue to identify the suggestion.
148148- Provide a ** step-by-step description of the suggested enhancement** in as many details
0 commit comments