You ever want to add a configuration file to a repository, but you want to 
mitigate the risk of sensitive information being included in an absent 
minded commit? Sure code reviews may help catch this, but wouldn't it be 
nice if there were some way to ensure that all commits for a specific file 
are deliberate?

What if you could track a file, then mark the file as read-only, so that 
subsequent changes to a file are ignored by git? When a new change needs to 
be committed, a flag is provided with the "commit" command, for instance 
"git commit --allow-write </path/to/read-only/file>".

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
To view this discussion on the web visit

Reply via email to