docs: add .gitignore to migration instructions
#6912
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What's the problem this PR addresses?
When following the step-by-step migration guide, I committed
.yarn/install-state.gzinto my repo. Turns out this is file isn't supposed to be committed, so here's a PR to add that to the migration steps.How did you fix it?
Added a link to the
.gitignoreFAQ.The raw Markdown numbers were also inaccurate (there were two
2.entries), so I also changed the list to just use1.for all entries.This change should render properly according to the Markdown spec, but adds more diff to the PR (in exchange for not needing to fiddle around with the numbers in the future). Let me know if that needs to be reverted.
Checklist