1

I've read about how people are using git update-index with --assume-unchanged to temporarily ignore some files that were "modified" but we don't want to ignore those modification.

For example, in my project I have some sort of launcher file, that comes with the standard launcher. but when the project is built locally, the launcher file's property might change but I want to "ignore" this. The usage of update-index --assume-unchanged is very tempting.

My question is, if I forget to retrack it back ie --no-assume-unchange it, and push it to remote, what are the implications?

Thanks

ALQH
  • 151
  • 2
  • 10

1 Answers1

4

My question is, if I forget to retrack it back ie --no-assume-unchange it, and push it to remote, what are the implications?

None (for the upstream repo): updating the index is a purely local operation, which isn't pushed at all.

Community
  • 1
  • 1
VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250