-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Split up release package & gh-pages build #231
Comments
This is great, thanks! Will try to do it if I get some time. |
Would I need to change any URLs in the files if I tried this? (pardon my ignorance, never used |
I'd like to give this a bump and offer to help, if necessary. Just had to go through diagnosing what was wrong with To get things a little more sane, the first thing you might want to do is just create a master branch and pull the current contents of gh-pages into it. After that, if the contents need to diverge (they probably should), let them. More importantly, though, I think it would help adoption if you just created the master branch and pulled the current gh-pages into it. |
Hi Rob, Thanks for offering to help. I don’t mind making the change, but I want something that won't add unnecessary future overhead for contributors. The Prism website currently has a downloader that needs access to all components to build the download. Therefore, the only way I see this working is if I can somehow point the master branch to be a subfolder of the website that updates automatically every time I commit to gh-pages. Themes and plugins though are on separate folders, so it gets more complicated. I really, really don't want to have to manually sync master and gh-pages after every single change though. |
Wouldn't you, instead, prefer to cut your downloads off master instead of
|
As I'm still subscribed to that ticket: A lot of tools (like package managers) are highly confused if there is no Also: If you add a |
A Gruntfile isn't really necessary, but would be great. I may just fork this project and get it done. If Lea takes a pull back, I'd really rather integrate Prism as a Bower component, NPM module or even Lea, you have two people now willing to jump in and help. Would you prefer -Rob On Mon, Jul 14, 2014 at 2:43 AM, Kaiser notifications@github.com wrote:
|
Wouldn't it be easier to just add a new branch
|
Well, that’s exactly what I don’t want to end up having to do. Keeping two things in sync manually is recipe for disaster. |
Forked. Thanks, Lea. I tried.
|
As I've been looking through the issues, this is a pretty hot topic (the whole I think #180 is where most of this talk is happening right now. Maybe we can close this issue as a duplicate? |
You're right. See #180 for discussion about this. |
The whole repo really needs a
master
andgh-pages
branch with different contents:gh-pages
-> build for the actual docs pagemaster
-> development source +dist
directory that holds thegh-pages
branchShort intro on how to split this one up:
master
branch:git branch -b master
git push origin master
(in case the remote repo is locally namedorigin
- one can check that by usinggit remote -v
).master
branch:git checkout master
dist
folder:mkdir dist
git add dist && git commit -m "distribution folder added"
dist
folder to thegh-pages
branch:git subtree push --prefix origin gh-pages
Done.
Now development can get split up between the actual releases and the page.
The text was updated successfully, but these errors were encountered: