chore(common): adds .gitignore to prevent noise from 16.0 changes #6782
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.
#6525's 🎡 chain made a lot of file system changes, and those are only going to be increasing with the 🎢 PRs. When swapping from
master
tostable-15.0
, without this in place...And that's before all the package-lock.json changes (for Web builds) kick in that need to be manually ignored during development!
Fortunately, one small
.gitignore
later, and we can mask all the 16.0+ tidbits with relative ease.@keymanapp-test-bot skip