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

Unable to run clean task #156

Closed
just-boris opened this issue Jan 13, 2017 · 5 comments
Closed

Unable to run clean task #156

just-boris opened this issue Jan 13, 2017 · 5 comments

Comments

@just-boris
Copy link

just-boris commented Jan 13, 2017

When I have made some changes in the configuration, the tool said me the following

Remote url mismatch.  Got "<something>" but expected "<something-else>" in node_modules/gh-pages/.cache. 
If you have changed your "repo" option, try running the "clean" task first.

I have tried to run gh-pages clean, but it didn't succeed. What kind of task should I run to clean the cache?

@kevincolten
Copy link

you can run rm -rf node_modules/gh-pages/.cache to clean the cache manually

@just-boris
Copy link
Author

Actually, there is a clean function exported from the code.

I wanted to do the same operation via CLI. If it is not possible now, I will be happy to send a PR. How about command?

gh-pages --clean

@paulcpederson
Copy link

@just-boris that function is in the lib, not in the cli.

@tschaub this tripped me up just now as well, but @kevincolten 's solution works well. I think it might be enough to just change the error message to:

Remote url mismatch.  Got "<something>" but expected "<something-else>" in node_modules/gh-pages/.cache. 
If you have changed your "repo" option, try clearing the cache by running:
  rm -rf node_modules/gh-pages/.cache

Let me know if you want me to open a pr with that change.

@newswim
Copy link

newswim commented Apr 18, 2017

Since I was using nvm I had to run

rm -rf ~/.nvm/versions/node/v7.6.0/lib/node_modules/gh-pages/.cache

@tschaub
Copy link
Owner

tschaub commented May 8, 2017

With the changes in #173, these cache collisions shouldn't be a problem any more. In addition, the package will now make a gh-pages-clean script available so people can remove all cached clones.

@tschaub tschaub closed this as completed May 8, 2017
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

5 participants