only gh-pages branch as primary branch

Question

only gh-pages branch as primary branch

Closed this issue 11 years ago · 6 comments

I think you'd get instant result by only having one branch, the gh-pagesbranch. By committing / pushing on this branch only, the latest modifications would instantly be published on http://n1k0.github.io/kept/, without having to merge from master.

I've done it on several other projects. It just works.

Answer 1 · 2014-05-28T20:09:57.000Z

Yup I've used that trick in the past, but as we're moving towards using a build system (see #10), that probably won't work. I'll just create a script for updating the gh-pages branch :)

As a side note, I would love avoiding to rely on a build system, but that's the price to pay with react…

Answer 2 · 2014-05-28T20:11:29.000Z

mmm... AFAICT, travis could do this for you, too.

Answer 3 · 2014-05-28T20:12:06.000Z

Lemme just write tests first ;)

Answer 4 · 2014-05-28T20:13:07.000Z

(oh, I see what you did there. Smart.)

Answer 5 · 2014-05-28T20:13:24.000Z

I'm not talking about tests, it's travis CI, as Continuous Integration: see https://medium.com/philosophy-logic/53a8270e87db

Answer 6 · 2014-05-28T20:14:15.000Z

Definitely smart. Will do. Can you please file an issue for this? :)