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
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.
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 86:
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 107:
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 113:
Enhancement suggestions are tracked as GitHub issues.
line 133:
A git client should be able to just take the url https://github.com/ActuallyTaylor/Open-Jellycuts 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 156:
If you had any issues throughout this process open an Issue and one of the maintainers will help you get everything resolved!
line 159:
Currently Open-Jellycuts does not have any documentation. If you want to create some, Awesome! Currently the sister project Open Jellycore uses the DocC documentation generation tool. Setting up DocC is fairly straightforward, the main part of documentation comes from adding documentation comments above all classes, structs and functions throughout the app.
The text was updated successfully, but these errors were encountered:
…orrect minor typo (#25)
#18
references to github.com/ActuallyTaylor were replaced by references to
github.com/OpenJelly
a couple of URL in the orginal had typos in URLs that were corrected by
adding a missing slash character
line 32
line 69
a minor typo of the word 'too' was replace by 'to'
line 138
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
Examples
line 32:
Open Jellycuts Code of Conduct.
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 69:
line 86:
line 107:
comment to the existing issue instead of opening a new one.
line 113:
Enhancement suggestions are tracked as GitHub issues.
line 133:
A git client should be able to just take the url
https://github.com/ActuallyTaylor/Open-Jellycuts
and properly clone all of the submodules. If youare missing submodules we recommend that you use the command line to clone instead of a client.
line 156:
line 159:
Currently Open-Jellycuts does not have any documentation. If you want to create some, Awesome! Currently the sister project Open Jellycore uses the DocC documentation generation tool. Setting up DocC is fairly straightforward, the main part of documentation comes from adding documentation comments above all classes, structs and functions throughout the app.
The text was updated successfully, but these errors were encountered: