Make gh-pages default, move remaining master content over, then delete?

Question

Make gh-pages default, move remaining master content over, then delete?

jancborchardt opened this issue 9 years ago · 10 comments

@Xaviju to make it simpler it would be good if we only use one branch, in this case gh-pages. Can you copy the remaining content of the master branch over?

cc @bnvk

Xaviju commented 9 years ago

Sure!

Answer 1 · 2015-04-29T19:48:17.000Z

@bnvk looks like you already moved and deleted it?

Answer 2 · 2015-04-29T21:13:06.000Z

Um @bnvk you just replaced what was on master (like your image and my writeup) with what was on gh-pages. So the other way around :\

Answer 3 · 2015-04-30T14:32:32.000Z

@bnvk so do you not want the stuff which was in here: https://github.com/opensourcedesign/events/tree/64f814c702e1b098b0bd11769f419dfcfc053527/2015-03-15%20Berlin%20Open%20Source%20Design%20meetup after all? We should add it to the events repo or somewhere, no?

After that we can remove the master branch.

Answer 4 · 2015-04-30T15:04:55.000Z

@jancborchardt ack, no, I didn't mean to do that. Thanks for catching it.

Answer 5 · 2015-09-01T23:19:55.000Z

What's the status of this?

Answer 6 · 2015-09-04T06:50:54.000Z

@bnvk is everything you need on gh-pages? Can you make sure and then remove master?

Answer 7 · 2016-12-11T22:05:28.000Z

This looks like its done?

Doing some cleaning..reopen if needed?
🏠 👷

Answer 8 · 2016-12-14T00:34:29.000Z

We actually no longer need to (and probably should not) be doing the gh-pages branch thing since Github now allows one to choose if one wants to use the master branch. For repos with code / app as well as a jekyll site this makes sense, but for our purposes we should just use master for all the repos IMHO

Answer 9 · 2016-12-15T14:11:47.000Z

@bnvk yup, agree with that as it makes stuff simpler. :) Also still I think it would help ease of organization and newcomers if we think about combining repos more. ;)