-
-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
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
Read .gitignore #1331
Comments
Currently, we use There's also |
Can it be that you mean the If I were you, I'd probably try to use the
You can create an issue but I wouldn't implement it for the sole reason that it wouldn't be a quick & fun thing for me to do - I didn't write Once a repo is available and paths within the repo are traversed, you should be able to prime the I hope that helps. |
@thomas-zahner fixed this. 🎉 |
Currently, lychee has its own
.lycheeignore
format.It’d be very nice if it could read the
.gitignore
, in order to avoid having to duplicate all information there.See also the discussion we had about our lychee usage at https://github.com/near/nearcore :)
The text was updated successfully, but these errors were encountered: