-
Notifications
You must be signed in to change notification settings - Fork 115
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
feat: Add --file-list <PATH>
to choose files to check
#708
Conversation
fdde0b3
to
4e82c55
Compare
This reverts commit fc7f517. This has two problems - This doesn't correctly handle spaces, likely needing crate-ci#708 - This overrides excludes, see crate-ci#347 This also has a weird cost/benefit balance because this requires enough repo history to do the analysis which takes time to pull down. Rather than waiting until the relevant changes are in to make this work, I'm pulling this out for now. Fixes crate-ci#806
Ehh. I don't know how to properly handle this on Windows. I don't know the platform, and it seems it might actually require checking the current system encoding and some other stuff like that? It's silly. Actual users could have been enjoying this feature for months now, and we stuck trying to support all these 0.7 users of Here is my solution for Windows users who need this feature: either submit a PR, or here is $0 needed to install a better operating system: 💵 . |
c66dc56
to
4ca840b
Compare
I have rebased on top of #837 which fixes one pain point of this PR I was hitting, so Would be nice if we could land. It's a really useful feature. Have been using it from my fork all this time. If there's anything other than obsolete OSes support, I'd be happy to address it. I would really fix it even for Windows if I could. I really have better thing to do than annoy you about it. 🤣 |
--stdin-paths
and -stdin-paths0
--file-list
e2b9743
to
358f44f
Compare
--file-list
--file-list <PATH>
to choose files to check
I believe the comments I just made are the extent of what is needed and I can merge after this. (nit: this would be a "feat" type, rather than a "chore" though this PR process might have felt like one...) |
Features are chores too. |
@epage done |
I'm curious, how do you define the "chore" type? I'm not seeing any more formal definition. I tend to use it for non-user-impacting project bookkeeping (e.g. changing CI pipelines). Or from another perspective, I view it as "this doesn't go in a changelog" while a |
I suck at conventional commits and I'm not even sure why I'm trying...
Makese sense. I should try to remember it. "Doesn't go in a changelog"... |
Fix #707
Just the draft as I had some time. Please feel free to take over if you'd like, I'm not sure if and when I'll find to finish.