Closed jbygdell closed 1 month ago
:warning: Please install the to ensure uploads and comments are reliably processed by Codecov.
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 39.17%. Comparing base (
bcb5721
) to head (c4d86c3
).
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Nice! I think it would be even nicer if the README was updated too, also if the precedence of the token was stated there.
Further, if I don't provide any token at all, I get Error: could not parse token, reason: token contains an invalid number of segments
. Would it make sense to add something more informative, like "No access token provided"..?
Nice! I think it would be even nicer if the README was updated too, also if the precedence of the token was stated there. Further, if I don't provide any token at all, I get
Error: could not parse token, reason: token contains an invalid number of segments
. Would it make sense to add something more informative, like "No access token provided"..?
That error comes directly from the CheckTokenExpiration
function.
But a check if any
token is supplied could probably fit somewhere.
Related issue(s) and PR(s)
This PR closes #395 .
Description This enables uploading of files where the token is not in the config file but supplied on the command line (
-accesToken
) or as an ENVACCESSTOKEN
. Token priority order:-accessToken
flagACCESSTOKEN
How to test
access_token
field-accesToken
flagACCESSTOKEN