-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add support for checking a package in a subdirectory #5
Comments
OK. I think we also need to update the readme for this parameter? |
Yeah that would be good. I'll send a follow-on PR to update the README. |
Oh, looks like you've already done that. Thank you! |
I just did this. Can you confirm if it now works for you?
Op wo 21 aug. 2024 23:52 schreef Bryce Mecum ***@***.***>:
… Yeah that would be good. I'll send a follow-on PR to update the README.
—
Reply to this email directly, view it on GitHub
<#5 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABUZ756NYW6FJR3GEJVQZLZSUD3RAVCNFSM6AAAAABL6BP42OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBTGA3TEOJUGQ>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
Sure, I'll test now. |
I ran it on my fork and it looks like it didn't set the source directory, see the raw log. Looking at it now. |
I think this may fix it: 6434f10 |
I think that did it. The docs make the two approaches sound equivalent at least for this use case. Thanks for fixing and for merging the PR! |
Hello! I'm interested in running recheck on a package that lives in a subdirectory of a repo and I think there's not currently a way to do this. Would you be interested in seeing a PR adding support for that?
The text was updated successfully, but these errors were encountered: