the fork is done (included an upstream branch to track mainstream changes) deleted lines of .gitmodule and the dir at vendor/plugins in the project git add && git commit the project git submodule add new forked repo git add && git commit check github => perfect make a cap to staging => works make cap to prod => works too
just to be right: all modifications I must do in the forked dir, not the submodule dir, right? regards, Fritzek On Oct 7, 10:13 pm, Fritzek <[EMAIL PROTECTED]> wrote: > Lucky me that I've never touched the corners of the curve ;-) > Cynthia, I was also frustrated. But always I've found a way around the > probs. I believe that was the reason why I've touched so much > functions or concepts of how to do. > If someone is interested I could briefly describe the way where 7 > bucks saves your hair to fade to grey. > The base concepts are great but mostly the details are evil enough to > drive you crazy. > So, lets start forking ... > > On Oct 7, 9:32 pm, Cynthia Kiser <[EMAIL PROTECTED]> wrote: > > > Quoting Fritzek <[EMAIL PROTECTED]>: > > > > I've started to use git 4 weeks ago and during this short period I've > > > used mostly every function of git. I'm a bit tiered of learning > > > another way to work with git. > > > Congrats! git does have a steep learning curve. I was definitely > > screaming with frustration at various points learning it - but it does > > get better - probably soon now. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
