I begin to use git for software development.
I have a project on github. This project also involves some user-settings stored in dedicated settings-files.
On
You can create a setting file like setting-sample
, and modify .gitignore
to ignore the real setting file (i.e. setting
). So the empty setting file will be kept in remote repo, and your personal setting file will be kept in your local repo.
You may commit the empty settings file and then commit a .gitignore file pointing to the original file, so in that case, the users would download the file but git will ignore the changes that users make.
In your personal branch, you could keep:
config.template
for example)That script is triggered on any git checkout
as a content filter driver.
That way, you can merge master
onto your personal branch as many time as you want, your config values will not be modified.