![]() ![]() Copy, add, status the not-to-be-tracked files.Debug if necessary with git-check-ignore.Make proper gitignore and gitattribute files.So the first (and somewhat unrealistic) Suggestion 1 The relevantĭont start a git project without creating a proper Main caveat: Moving a file from tracked to ignored is somewhat non-trivial - simply adding the suitable pattern to gitignore wont cut it once tracked.Ignoring is nearly as easy - just make sure it matches something in your gitignore file.Just do nothing…other than using git! And any file is tracked. Technically your requirement is contradictory.Īt a more philosophical level it (seems) to be a clash between open source and corporate philosophy.Īnyhow… I'll suggest some things that come to my mind It's less effective in scenarios where will be frequently changing, since it then falls on the user to notice any changes and manually merge them into the local foo.cfg. In your case, since the config files are for a third-party plugin, this could work, since they're probably pretty stable. One hacky workaround which I've seen several projects use is to make a sanitized copy of foo.cfg named, track in git, gitignore foo.cfg, and rely on the user to copy to foo.cfg after cloning and customize it (adding authentication credentials, personalized settings, etc.). production settings, as well as site-specific settings, and this caused repeated adverse effects for our production systems. In our case, some of the differences were development vs. I have personal experience with this one, and it's a major, ongoing nuisance to deal with. Site-/developer-specific settings don't raise the security issues that authentication information does, but they will still cause issues if multiple sites or developers are involved because, even if you have a policy against committing/pushing changes to those files, it's just a matter of time before someone commits them and causes everyone else's settings to be changed (or spurious conflicts to be generated) the next time they pull. ![]() Even if the credentials have been removed at some future point, they'll still be available in the history. If there is any chance that your git repo will ever be made accessible to outside or untrusted entities, then your authentication details should not be in it because they will be disclosed to anyone who clones the project. If I'm reading your question correctly, and the files in question contain such things as authentication credentials and site- or developer-specific configuration settings, then this is the way to go. Ask all my team members to add these files back to their local project with their own settings. Remove these files from git repository. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |