Closed sstevens2 closed 6 years ago
Yeah I think that would be right move in terms of keeping a clean history, but it's a little tricky because this would require a force push at some point to rewrite the history the gh-pages
branch (I think). I still think its the way to go so that future updates to those lessons can be incorporated here though if you're comfortable with it.
To make future updates easier, I think I'd recommend making a gh-pages-upstream
branch in this repo that is always in sync with the latest swc lessons. The served gh-pages
branch here will always be based on that.
So the steps would be:
gh-pages
branch under a new name (gh-pages-upstream
or something like that)gh-pages-upstream
to this reapogh-pages
branch of this repo onto gh-pages-upstream
and handle any conflictsand then it should be all set! Fingers crossed for no conflicts...
Maybe you can walk me through this tomorrow at the meeting?
Sure thing!
Hey @pshriwise I was thinking it would be nice to update our version of the lessons to the lastest swc ones. I went through some which I could easily diff and most of the changes were small but nice improvements. I'm thinking maybe this could be done with a rebase but as I've never done one before I could use some advice. What do you think? Sarah