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
CONTRIBUTING.md has many URLs with refereces to Legacy "ActuallyTaylor" repo instead of "OpenJelly". Likelly want to change for consistency of branding
To Reproduce
search for "github.com/ActuallyTaylor" or "actuallytaylor.github.io" in CONTRIBUTING.md
If you want to ask a question, we assume that you have read the available Documentation.
line 41
Before you ask a question, it is best to search for existing Issues that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.
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. If you are looking for support, you might want to check this section).
line 65
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.
line 82
Open an Issue. (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.)
line 104
Read the documentation carefully and find out if the functionality is already covered, maybe by an individual configuration.
line 105
Perform a search 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.
line 111
Enhancement suggestions are tracked as GitHub issues.
line 131
A git client should be able to just take the url https://github.com/ActuallyTaylor/Open-Jellycore.git and properly clone all of the submodules. If you are missing submodules we recommend that you use the command line to clone instead of a client.
line 137* also note "uou" vs "you"
Whenever uou make a contribution you should make sure you also are improving the documentation. Open Jellycore is almost completely documented using DocC. This documentation is then generated and uploaded to the documentation site https://actuallytaylor.github.io/Open-Jellycore/documentation/open_jellycore/. When you create new parts of Jellycore be sure to document as you go!
The text was updated successfully, but these errors were encountered:
Describe the bug
CONTRIBUTING.md has many URLs with refereces to Legacy "ActuallyTaylor" repo instead of "OpenJelly". Likelly want to change for consistency of branding
To Reproduce
search for "github.com/ActuallyTaylor" or "actuallytaylor.github.io" in CONTRIBUTING.md
Expected behavior
expect to stay within the "OpenJelly" repo
Examples
line 32
Open Jellycore Code of Conduct.
line 39
line 41
Before you ask a question, it is best to search for existing Issues that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.
line 45
line 64
line 65
line 82
line 104
line 105
line 111
Enhancement suggestions are tracked as GitHub issues.
line 127
git clone --recursive https://github.com/ActuallyTaylor/Open-Jellycore.git
line 131
A git client should be able to just take the url
https://github.com/ActuallyTaylor/Open-Jellycore.git
and properly clone all of the submodules. If you are missing submodules we recommend that you use the command line to clone instead of a client.line 137* also note "uou" vs "you"
Whenever uou make a contribution you should make sure you also are improving the documentation. Open Jellycore is almost completely documented using DocC. This documentation is then generated and uploaded to the documentation site https://actuallytaylor.github.io/Open-Jellycore/documentation/open_jellycore/. When you create new parts of Jellycore be sure to document as you go!
The text was updated successfully, but these errors were encountered: