You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Consider the following example
.gitignore: data/locks
Now if you try to: echo some_text > data/locks/some_file.txt you'll get Permission denied
According to git documentation:
gitignore - Specifies intentionally untracked files to ignore
In my case data/locks is part of docuwiki setup, all files in this directory as well as in data/tmp and data/cache should be writable, but ignored-untracked by git repository
The text was updated successfully, but these errors were encountered:
vegaminer
changed the title
Incorect handling of .gitignore. Unable to create a file wich matches against a gitignore rule
Incorect handling of .gitignore. Unable to create a file which matches against a gitignore rule
Nov 26, 2018
vegaminer
changed the title
Incorect handling of .gitignore. Unable to create a file which matches against a gitignore rule
Incorect handling of .gitignore. Unable to create a file which match against a gitignore rule
Nov 26, 2018
vegaminer
changed the title
Incorect handling of .gitignore. Unable to create a file which match against a gitignore rule
Incorect handling of .gitignore. Unable to create a file which name match against a gitignore rule
Nov 26, 2018
Looks like this behavior was introduced at #99
Consider the following example
.gitignore:
data/locks
Now if you try to:
echo some_text > data/locks/some_file.txt
you'll getPermission denied
According to git documentation:
In my case data/locks is part of docuwiki setup, all files in this directory as well as in data/tmp and data/cache should be writable, but ignored-untracked by git repository
The text was updated successfully, but these errors were encountered: