Skip to content
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

🚀 Feature: Allow specifying a CODECOV_TOKEN #1848

Closed
2 tasks done
JoshuaKGoldberg opened this issue Jan 14, 2025 · 0 comments · Fixed by #1865
Closed
2 tasks done

🚀 Feature: Allow specifying a CODECOV_TOKEN #1848

JoshuaKGoldberg opened this issue Jan 14, 2025 · 0 comments · Fixed by #1865
Assignees
Labels
status: accepting prs Please, send a pull request to resolve this! type: feature New enhancement or request

Comments

@JoshuaKGoldberg
Copy link
Owner

Bug Report Checklist

Overview

Following the, ah, unexpected work around #1303, I've started populating a CODECOV_TOKEN in my repos:

- env:
CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}
if: always()
uses: codecov/codecov-action@v3

I'll want to add this in as an option so that template consumers -including my other repos- can have it be set for them as part of templating.

Additional Info

I don't think this needs to be done by default for all users. I keep getting 429s from the Codecov service because I have dozens of repos. Most people don't need this by default and wouldn't benefit from having the getting-started steps also ask them to set this up.

That being said, it would be a nice followup to see if that token can be made automatically through the API...

💖

@JoshuaKGoldberg JoshuaKGoldberg added type: feature New enhancement or request status: accepting prs Please, send a pull request to resolve this! labels Jan 14, 2025
@JoshuaKGoldberg JoshuaKGoldberg self-assigned this Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: accepting prs Please, send a pull request to resolve this! type: feature New enhancement or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant