Skip to content
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

make gh-pages shouldn't check in files not in git manifest #17

Open
ivanov opened this issue Feb 21, 2013 · 3 comments
Open

make gh-pages shouldn't check in files not in git manifest #17

ivanov opened this issue Feb 21, 2013 · 3 comments
Milestone

Comments

@ivanov
Copy link
Member

ivanov commented Feb 21, 2013

No description provided.

@takluyver
Copy link
Member

I'm not familiar with git terminology, but it sounds like you're suggesting it should only upload changed files, not new files?

@ivanov
Copy link
Member Author

ivanov commented Feb 22, 2013

that's right. It's a bit weird how make gh-pages works, in that you run it from one repo (the one this issue is on) but it also creates commits in another repo (ipython.github.com - the one we serve, which is called gh-pages locally). The problem is that the way this currently happens, we just wholesale copy everything in this repos directory (whether or not it is checked into git), and check it into the gh-pages repo.

@takluyver
Copy link
Member

I don't think we should need a separate command to add a file to the website - that's common enough (for images etc.) that I want it to be simple.

As I see it, the second git repository is just an implementation detail - the process to upload the built website happens to be pushing it to a git repository, but the make target would work the same way if it were using rsync, say.

If things are getting uploaded incorrectly, I think the point to address that is the build process which puts them into the destination folder. Once they're in there, they're fair game for uploading.

@Carreau Carreau added this to the wishlist milestone Sep 21, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants