-
Notifications
You must be signed in to change notification settings - Fork 207
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
Globs not supported in v2? #770
Comments
The current version is v3 and they did not bother to reply or to mention in docs if glob patterns are allowed. |
From personal experiments, globs aren't supported in v3. |
@thomasrockhu Any chance to get a pair of eyes on this one. Forcing people to use only hard-coded file paths instead of being able to use glob patterns for the files to be collected is a huge regression. |
@dyladan @ssbarnea ok, I made some changes here to how we handle globs. I would recommend trying I'm going to push towards our community boards because I check that more frequently. If the above doesn't work, please ping me there and I'll do what I can to fix it. |
@thomasrockhu-codecov This issue is still present. Your suggested
When the files are specified explicitly, the logs looks like this:
I also couldn't find any glob related change in the release notes or merged pull request list. Where did you made your "changes"? |
For people coming here from Google, you can use |
@lishaduck Can you please point to the respective documentation? I mean, it would be nice to see at least one working example using globs. It should then be added to the documentation. (FTR, I already use |
@lishaduck Thank you! I need to try it again, then. If it works now, it must be rather newish, since I definitely tried a single |
I think globs still don't work. But since no valid files where given, the action falls back to file search, which probably works for you. Here is part of your log:
And here is my log:
The |
Ah, I didn't know it did that.
That's a really silly default. Well, back to manually writing them, I guess 😢 |
@thomasrockhu-codecov Please reopen this issue. |
@joseph-sentry Can you please reopen this issue? |
A lerna monorepo consists of many packages in a single git repository. They are typically each in a folder in the
packages/
directory. After my tests run, coverage reports are generated in the./coverage
folder of each subproject.I am attempting to upload coverage for lerna monorepo using the following configuration:
But no coverage files are found. Full log output:
The text was updated successfully, but these errors were encountered: