-
Notifications
You must be signed in to change notification settings - Fork 9
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
GHA v4 does not work well when run from workflow_run instead of pull_request #273
Comments
@thomasrockhu-codecov can you take a look at this once you're back in? |
## PR Checklist - [x] Addresses an existing open issue: fixes #1303 - [x] That issue was marked as [`status: accepting prs`](https://github.com/JoshuaKGoldberg/create-typescript-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22status%3A+accepting+prs%22) - [x] Steps in [CONTRIBUTING.md](https://github.com/JoshuaKGoldberg/create-typescript-app/blob/main/.github/CONTRIBUTING.md) were taken ## Overview codecov/codecov-action#1292 & codecov/feedback#273 make me not want to deal with this token stuff until it's all resolved. Things were working fine before, and I really don't want to add a _third_ token requirement to repos made with `create-typescript-app`.
Ok, I did a run on a This leads me to believe there is something else happening. @kdarkhan @adamjstewart @melink14 @JoshuaKGoldberg, if you have any logs or a link that you could point me to, I'd be happy to look in and see why the action@v4 is not working |
Thanks for asking! All of my repos that use the Codecov action should be open source. JoshuaKGoldberg/create-typescript-app#1289 -> JoshuaKGoldberg/create-typescript-app#1303 -> JoshuaKGoldberg/create-typescript-app#1304 should be the main references for that repository in particular. If there's any logstuffs you don't have access to, I'd be happy to provide them. That repo also is a GitHub repo template you can use to make a new repo to test for yourself. LMK if that's not clear how to use here either 🙂 |
You need to add the token as a secret and as an argument to the |
Uh, from what I can tell, this was triggered by thomasrockhu-codecov/example-python#1, which is not from a fork. Also, the "Download coverage artifacts" step failed to find and download anything. Therefore I would be pretty surprised if the "Upload coverage to codecov" step was doing anything useful. In my testing, I was able to get both of those steps working correctly. The issue I encountered was that |
@adamjstewart got it, is this specifically in PRs from forks only then? |
I guess I've never tried a PR from upstream since we don't usually get any out those for open source repos. |
got it, @adamjstewart I'm not sure this is a specific |
@adamjstewart I see the problem, the issue was due to rate limiting. Have you installed the Codecov app on your fork? |
@thomasrockhu-codecov the rate limiting issue was the reason for opening #126. The reason we're using |
@adamjstewart I'm going to close this as I believe it's been fixed. However, if you feel that isn't true, please feel free to create a new issue and tag me. |
#126 (comment)
Related issues
Error: Codecov token not found
in a PR from a fork to a pubilc repo codecov-action#1292The text was updated successfully, but these errors were encountered: