Well, yes, and no…
I understand that you want your local copies to “override” what’s in the remote, but, oh, man, if someone has modified the files in the remote repo in some different way, and you just ignore their changes and try to “force” your own changes without even looking at possible conflicts, well, I weep for you (and your coworkers) 😉
That said, though, it’s really easy to do the “right thing…”
Step 1:
git stash
in your local repo. That will save away your local updates into the stash, then revert your modified files back to their pre-edit state.
Step 2:
git pull
to get any modified versions. Now, hopefully, that won’t get any new versions of the files you’re worried about. If it doesn’t, then the next step will work smoothly. If it does, then you’ve got some work to do, and you’ll be glad you did.
Step 3:
git stash pop
That will merge your modified versions that you stashed away in Step 1 with the versions you just pulled in Step 2. If everything goes smoothly, then you’ll be all set!
If, on the other hand, there were real conflicts between what you pulled in Step 2 and your modifications (due to someone else editing in the interim), you’ll find out and be told to resolve them. Do it.
Things will work out much better this way – it will probably keep your changes without any real work on your part, while alerting you to serious, serious issues.