This repository was archived by the owner on Dec 5, 2024. It is now read-only.
Update getting-started.md #893
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Removed unfinished 4th step for # setting up a new repository
Deleted # connecting to an existing repository
I'm not sure when this case would arise as the proper workflow should have the unity project with plugin in a repository, never the project alone.
Added steps for # Connecting to an Existing Repository that already has the GitHub for Unity package
These are based on what worked for me today.
|
Did just notice that the top of the file has a link to that header. So up to you to delete or save it |
|
Hey @dragonfyre23 I'm going to merge your commit to #897 and make some more tweaks. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the Change
Updated documentation in getting-started.md
Removed unfinished 4th step for # setting up a new repository
Deleted # connecting to an existing repository
I'm not sure when this case would arise as the proper workflow should have the unity project with plugin in a repository, never the project alone.
Added steps for # Connecting to an Existing Repository that already has the GitHub for Unity package
These are based on what worked for me today.
Alternate Designs
You may want to not remove the header # Connecting to an Existing Repository for some reason
Benefits
Clarity for new users who wish to use multiple machines to work on a project (the main functionality of GitHub)
Possible Drawbacks
None, just editing text here
Applicable Issues
Issue #891