-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Small typo in IPython developer’s guide #270
Comments
I've checked that, and made the change to the sources (since it's trivial, I figured that it makes more sense to get it committed straight away than to worry about someone reviewing the change). The docs will need to be rebuilt and uploaded - does someone want to give me a pointer on the best way to do that? Or is it best just to leave it until there are some other changes to the docs? |
No, go ahead and do it yourself. Sorry that we haven't added instructions on this, it's the brand new setup we put in this week. In the docs/ directory, run (just once) ./gh-pages.py. That will checkout a sub-repo in a directory called gh-pages/. Then run 'make gh-pages'. It should do a build and commit, and leave the gh-pages repo ready for a push. You then just need to look in gh-pages that index.html looks reasonable and if you're happy with the result, 'git push' it. That should be it. BTW, if you can add these short instructions to the dev guide on a small section on how to handle the docs, that would be great. |
./gh-pages.py gives me:
Running
|
Sorry, if there's no tag you should do ./gh-pages.py Current or similar, so that it doesn't try to get a tag. We should probably fix the gh-pges script to do that automatically when there's no argument and no tag. |
I'm having more troubles, I'll take this back to the list. |
Sorry... I'm also on IRC if you need me, we obviously need to smooth this out a little bit more :) |
The typo is now well and truly fixed. |
Part "Setup your fork", In "Overview":
git clone git@github.com/your-user-name/ipython.git
The first "/" should be replace by ":"
The text was updated successfully, but these errors were encountered: