-
Notifications
You must be signed in to change notification settings - Fork 306
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
"state" not being writable #3
Comments
ok, this one is due to github not handling empty directories, i'll add code to create it if not found, thanks for spotting |
That's actually git, not github - the way to do that is to create a .gitignore file which says "ignore every file in this directory except the .gitignore file itself". It would look like this:
Git will then commit the directory since it's not empty (but it will ignore all the cache/other files in that directory). One good thing about git is that it will also commit the permissions, so if you chmod the dir 777 and commit it, then I clone your repo, the directory has the same file permissions on my machine as on yours. I was pretty resistant to git at first myself, its more complex than SVN... but I find myself more productive with git than SVN once I got the hang of it. |
Normally you would use a .gitkeep file for this |
Upon installing it gives an error about "state" not being writable, which doesn't exist. I have to create it & then make it writable. You should have it automatically create it, or check the empty folder into VCS.
The text was updated successfully, but these errors were encountered: