I have a central repository with a subset of files that I want to protect from being changed (by pushing) from other users. If I add these files to .gitignore,
Is there a specific reason why Git must itself be the answer to this?
How about making the files read-only, and dictating as policy that these files shouldn't be pushed?
Sometimes a technological solution is not the simplest way.
If somebody does push changes to these files, these changes can always be reverted.