2
\$\begingroup\$

I've just installed the Unity quick search package. This is an editor extension which each developer should choose if they want installed or not. My problem is that because this was added as a package it also made changes to my project which would end-up in our repository.

The changes are:

Project root/
|── Assets/
|   |── Assets.index
|   └── Assets.index.meta
|── Packages/
|   |── manifest.json
|   └── packages-lock.json
|── UserSettings/
    └── QuickSearch.settings

Questions:

  1. Should this files be added to source control?
  2. How can I ignore the changes in manifest.json and packages-lock.json without filters?
\$\endgroup\$
3
  • \$\begingroup\$ Any specific reason to not add "quick search" in your repository? \$\endgroup\$ – Digvijaysinh Gohil Aug 20 '20 at 16:15
  • \$\begingroup\$ @DigvijaysinhGohil because it's personal decision whether to use it or not. It's the same as forcing a team member to use the same shortcuts as me. And also because the application can work at runtime and can also be compiled without that package istanlled. \$\endgroup\$ – Bobby Tables Aug 20 '20 at 19:32
  • \$\begingroup\$ Only solution I can think of right now is either don't upload your manifest entirely or create another branch and at merge time stash your menifest, in both cases when you pull you have to re-add your package again. This is not the solution but until you find one this might help. \$\endgroup\$ – Digvijaysinh Gohil Aug 22 '20 at 6:39

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.