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 Mar 23, 2023. It is now read-only.
FYI, erroring out or prompting at a missing file would break @brikis98's suggestion here to ignore a file that is already present. There is no other way that I know of to ignore a file.
So I would suggest that if erroring out, etc. is added as an enhancement, then an option to ignore a file that's already present be added at the same time.
I'm not sure it makes sense to error out of a file you asked to ignore doesn't exist. Most other systems don't do this: e.g. .gitignore or .dockerignore. At most, a warning could be useful.
I'm not sure it makes sense to error out of a file you asked to ignore doesn't exist.
To clarify, he's suggesting that it error out if the file you provide that specifies which files to ignore doesn't exist (e.g. the .dockerignore file) -- not if some of the files the .dockerignore file references don't exist.
As by the story from #99,
-i
option could use validation. If the ignore file does not exist at the path, there should be an error (or prompt).The text was updated successfully, but these errors were encountered: