On Thu, May 17, 2012 at 10:58:01AM -0700, psychok7 wrote: > ok so basically what you are saying is that everything i clone my repo i > will need to had my heroku reference.. well i figured that part out just > thought there would be an easier way > > On Thursday, May 17, 2012 5:48:18 PM UTC+1, Steven! Ragnarok wrote: > > > > On Thu, May 17, 2012 at 09:19:05AM -0700, psychok7 wrote: > > > So i have this project hosted on bitbucket and i added a git remote > > > reference saying that origin is bitbucket > > > after i added a heroku remote reference and everything is good. > > > > > > when i pushed my changes into bitbucket and latter cloned it the heroku > > > reference was not there, only bitbucket. > > > > > > why is that? how do i fix this? > > > > > > thanks > > > > Remotes are not part of a git repository itself but rather part of the > > configuration information of an indvidual repository clone. > > > > There's lots of good reasons for this. It would be a pretty big > > information link if all your remote names were exposed. > > > > When you clone from BitBucket, all you need to do in the new clone is > > > > `git remote add heroku [email protected]:appname.git` and you can then push > > to Heroku happily. > > > > If you for some reason have a lot of clones of a repo on a single > > machine, consider using branching rather than cloning as a way of > > differentiating different development paths. > > > > > > -- > > > You received this message because you are subscribed to the Google > > > Groups "Heroku" group. > > > > > > 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_US?hl=en > > > > -- > > Steven! > > nuclearsandwich > > > > -- > You received this message because you are subscribed to the Google > Groups "Heroku" group. > > 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_US?hl=en
Not to my knowledge. As I said before, bundling all your remotes and sending them to every remote repo would be a substantial information leak. Since remotes are not git objects (they're part of a repository's configuration) there's no way to force them to push to a remote repo the way you can force tags to push. -- Steven! nuclearsandwich -- You received this message because you are subscribed to the Google Groups "Heroku" group. 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_US?hl=en
