Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

legacy url links to ActuallyTaylor repo instead of OpenJelly repo in CONTRIBUTING.md #16

Open
chrysaora-achlyos opened this issue May 23, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@chrysaora-achlyos
Copy link

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

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.

line 45

line 64

  • 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 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!

@chrysaora-achlyos chrysaora-achlyos added the bug Something isn't working label May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant