We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi! We should make all the file patterns in .gitignore start with a slash, in order to make it predictable where they match. Example:
.gitignore
$ mkdir yolo $ mkdir yolo/cover $ touch yolo/cover/ohno $ git status yolo/ On branch implement-yolo nothing to commit, working tree clean
… which may cause accidential data loss in the ohno file. (Because the cover/ ignore rule matches in all subdirectories.)
ohno
cover/
The .history line should have a comment that describes it saves the prompt history, without replies.
.history
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi! We should make all the file patterns in
.gitignore
start with a slash, in order to make it predictable where they match. Example:… which may cause accidential data loss in the
ohno
file. (Because thecover/
ignore rule matches in all subdirectories.)The
.history
line should have a comment that describes it saves the prompt history, without replies.The text was updated successfully, but these errors were encountered: