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
{{ message }}
This repository has been archived by the owner on Dec 16, 2019. It is now read-only.
I largely stick to the practice of be exact with ignores. People should stick check git status and not rely on magic. The gitignore just means you can follow a process of git status, check things out, then git add -A.
Being too inexact may ignore things that repeat later on that are wanted and also hide things/lose being able to see new things pop up. Though clocking a pattern like *.lo (extensions/file types) tends to be quite reliable for binary types.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Would be nice to have some build spam hidden in gitignore.
I largely stick to the practice of be exact with ignores. People should stick check git status and not rely on magic. The gitignore just means you can follow a process of git status, check things out, then git add -A.
Being too inexact may ignore things that repeat later on that are wanted and also hide things/lose being able to see new things pop up. Though clocking a pattern like *.lo (extensions/file types) tends to be quite reliable for binary types.
The text was updated successfully, but these errors were encountered: