The route many people take is to provide a sample file that is tracked, and
add the actual file to .gitignore. Another option would be to just add the
settings file to .gitignore, and have your code generate the settings with
default values if it is not present.
Tekkub
Github General Support
http://support.github.com/
Join us on IRC: #github on freenode.net
Discussion group: [email protected]
On Fri, Jan 30, 2009 at 11:29 AM, JesseD <[email protected]> wrote:
>
> Hi all, I have a question about doing something that maybe you can
> help with.
>
> I have a repository with a settings file, which has a bunch of lines
> of... you guessed it... settings:
>
> logAllRequests = True
> logHeaders = False
> etc...
>
> Now, when someone clones the repository I want them to get this file
> with the default values.
>
> When someone adds new lines to this file (new settings), I want those
> to be committed.
>
> But changes to existing lines, I want to be ignored, so if someone
> changes one setting from False to True, that change should be ignored
> in the commit (to prevent polluting the default value).
>
> Is there any way to do something like this?
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"GitHub" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/github?hl=en
-~----------~----~----~----~------~----~------~--~---
