A
A
Alexey Chertok2019-07-23 16:56:55
git
Alexey Chertok, 2019-07-23 16:56:55

What is the correct way to write gitignore for paths?

Hello. Help to correctly compose gitignore .. because when commit and push swears on the way.
Now my file paths are set like this:

<link rel="stylesheet" type="text/css" href="{STYLES_DIR}/default.engine.css">
<script src="{JAVASCRIPT_DIR}/jquery.model.js"></script>

But since the paths for GIT are not visible, "cannot resolve file" swears.
Can I somehow set a condition so that it ignores ?

Answer the question

In order to leave comments, you need to log in

1 answer(s)
L
lorc, 2019-07-23
@lorc

From "man gitignore":
• If the pattern ends with a slash, it is removed for the purpose of the following description, but it would only find a match with a directory. In other words, foo/ will match
a directory foo and paths underneath it, but will not match a regular file or a symbolic link foo (this is consistent with the way how pathspec works in general in Git).
• If the pattern does not contain a slash /, Git treats it as a shell glob pattern and checks for a match against the pathname relative to the location of the .gitignore file
(relative to the toplevel of the work tree if not from a . gitignore file).
• Otherwise, Git treats the pattern as a shell glob: "*" matches anything except "/", "?" matches any one character except "/" and "[]" matches one character in a selected
range. See fnmatch(3) and the FNM_PATHNAME flag for a more detailed description.
• A leading slash matches the beginning of the pathname. For example, "/*.c" matches "cat-file.c" but not "mozilla-sha1/sha1.c".
There are also examples in the mana:

# exclude except everything directory foo/bar
/*
!/foo
/foo/*
!/foo/bar

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question