document Restoring Packages after a Fresh Checkout #720
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
…ME.md with instructions for handling missing NuGet packages after clone
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Document so #719 is clarified.
Add a new section to the README, "Restoring Packages after a Fresh Checkout", to clarify what to do when NuGet packages are missing after a fresh clone or checkout. The section describes two main options:
Option 1: Restoring packages using the NuGetForUnity CLI (recommended for CI/CD), with a link to the relevant section.
Option 2: Ignoring compile errors on first Unity startup (recommended for developers), with clear step-by-step instructions.