On Wed, Oct 29, 2008 at 4:28 PM, Markus Prinz <[EMAIL PROTECTED]> wrote: > > On 29.10.2008, at 22:09, jgeiger wrote: >> >> 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. > > Technically you can achieve that with a public repo on GitHub, and > your local repo. Any changes you make to your local repo are going to > stay that way, and then, if you feel like it, you can push to GitHub, > thus making it public.
In particular, look into git's rebase command; using rebase --interactive, you can rearrange and compress changesets in your history before pushing to GitHub. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to github@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
