On Oct 29, 2:09 pm, jgeiger <[EMAIL PROTECTED]> wrote: > I'm trying to find a best practice for hosting a project that needs > private development, but also needs the code to be publicly > accessible. > > I'm thinking about setting up 2 repositories, 1 public, 1 private, > doing all the work on the private shared repository, and when creating > a "release", copying the code from my local private to my local > public, committing and pushing. > > Essentially I'm trying to hide the daily internal workflow of the > commits and changes while providing a public base that can be > controlled for things like database settings, keys, etc.
Are branches that get squashed insufficient? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
