9

I'm writing an iOS app that uses a versioned Core Data model.
I just very nearly released a version of the app which crashed on upgrade because I'd accidentally edited the old version as well as creating a new one.

To stop this happening again, I'd like to flag the old versions in some way that prevents any check-in that modifies those files without first removing the flag.

To make things more complicated, I'm using git-svn, so having a read-only repo as a submodule won't work.

CodeWizard
  • 128,036
  • 21
  • 144
  • 167
Simon
  • 25,468
  • 44
  • 152
  • 266

4 Answers4

3

Basically you cant.
Git will track changes done with chmod if you did not turn the flag off.

You can use some workaround to do it.

  • Git hook

    Verify in your both local & server hooks that the desired file is not part of the diff which means that it was not modified.

    Why in both?

    Since local hooks can be removed y user so you want to verify it in the server. can be done in the pre-receive or update hooks.

  • Read-only submodule

    Place the file in a separate repository and use it as submodule. This repository will be read-only for all users except the ones which you allow to write to.
    I don't know what is your git server but most of the servers support read only or lock to any given branch.

  • git update-index --assume-unchanged

    it makes Git to omit any checking and assume it has not changed. When you make changes to working tree files, you have to explicitly tell Git about it by dropping "assume unchanged" bit, either before or after you modify them.

This will "ignore" any local changes made to this file.

CodeWizard
  • 128,036
  • 21
  • 144
  • 167
  • Could you go into a bit more detail about how `git update-index` works? Can I give it the old model versions as an argument? Will the assumption survive commits? – Simon Nov 29 '15 at 14:06
0

Initialize a new repo with read-only access and add it as a submodule

dimid
  • 7,285
  • 1
  • 46
  • 85
0

Have you considered tagging your versions? Tags are like read-only branches. You can move the tag pointer to a different branch but you'll have to use the force (-f) option so you'll at least have to think about what you're doing, you won't be doing it by accident. Here is a good reference on git tagging: https://git-scm.com/book/en/v2/Git-Basics-Tagging

Ricky Nelson
  • 876
  • 10
  • 24
-2

What about chmod 400 /path/to/file?

Vash2593
  • 129
  • 3