Thanks for that link! This is much cleaner than how I did this last time, which involved making patch files out of my whole history after the offending change and was kinda nasty. This approach actually looks pretty clean. -Mat
On Apr 3, 2009, at 11:02 AM, Max A wrote: > Here's more about that "somehow" part: > http://github.com/guides/completely-remove-a-file-from-all-revisions > > On Apr 2, 5:39 am, redronin <[email protected]> wrote: >> Mat, >> Thanks for the info and link. I'll give a try this weekend. >> >> John. >> >> On Apr 1, 11:11 am, Mat Schaffer <[email protected]> wrote: >> >>> On Apr 1, 2009, at 10:56 AM, redronin wrote: >> >>>> Hi, >>>> I have an app on Heroku which I want to open-source and post onto >>>> Github. >> >>>> I have a number of config files which I wish to remove from the >>>> repository before I push to Github. >> >>>> How is it possible to .gitignore certain files (so it doesn't >>>> show up >>>> in Github) but at the same time be able to deploy to Heroku? >> >>>> Is this possible? I thought creating a separate deploy or github >>>> branch would do it, but in github you are able to see all the >>>> branches. Is there a setting or command in Github that will limit >>>> what >>>> branches are available? Or is there some configuration in Heroku >>>> that >>>> can manage this? >> >>>> My only other idea was to create a whole separate repository for >>>> Github....not really ideal. Any ideas? >> >>>> Thanks! >>>> John. >> >>> I'm pretty sure what you're asking about is addressed here: >> >>> http://groups.google.com/group/heroku/browse_thread/thread/d7b1aecb42 >>> ... >> >>> But the issue in your case is that the repository history already >>> contains those files so you can't just push the repo (and it's >>> history) to github without first removing them from the history >>> somehow. >> >>> If you're not too worried about starting a new repo and losing old >>> history, that would be easiest. Basically start a repo on github and >>> import just the open stuff. Then branch that as "heroku" and add in >>> the heroku specific config stuff. Then push that heroku branch to >>> heroku/master (as in the thread). >> >>> If it's really important that you maintain history, the only way I >>> know to do it is to make patch files of all your commits back to the >>> one you added the config file in. git reset to just before that >>> commit, then replay the patches but not the config file. It's kind >>> of >>> a pain and it'll also require that any clones (like those on >>> github or >>> heroku) get recreated (by way of git push --force probably). >> >>> Hope that helps and isn't too confusing. >>> -Mat > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Heroku" 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/heroku?hl=en -~----------~----~----~----~------~----~------~--~---
