-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
DOC: Try with new token #16389
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
DOC: Try with new token #16389
Conversation
just go ahead and merge |
Codecov Report
@@ Coverage Diff @@
## master #16389 +/- ##
==========================================
- Coverage 90.42% 90.4% -0.03%
==========================================
Files 161 161
Lines 50997 50997
==========================================
- Hits 46116 46104 -12
- Misses 4881 4893 +12
Continue to review full report at Codecov.
|
1 similar comment
Codecov Report
@@ Coverage Diff @@
## master #16389 +/- ##
==========================================
- Coverage 90.42% 90.4% -0.03%
==========================================
Files 161 161
Lines 50997 50997
==========================================
- Hits 46116 46104 -12
- Misses 4881 4893 +12
Continue to review full report at Codecov.
|
this was with the previous address (just moved the repo). I think you have to use the token of the remote you are pushing to (e.g. pandas-dev/pandas-docs-travis), and not where you are pushing from |
I think I have to update |
I moved the docs back for now. But, anyhow, the authentication was still failing ... |
Let's see if this works @jreback.
I think you have to be in the
pandas
git repo when youtravis-encrypt
, since that's the Travis build that's accessing the env var.