Closed dharhas closed 4 years ago
I created a new branch to address this issue. I created a new key and tested it and it is writing files to the gh-pages branch. I'm not sure if something is happening when you try to pull it to the master?
Do a PR with the new key and I can merge to test.
On Sun, Sep 22, 2019, 11:19 PM ppwadhwa notifications@github.com wrote:
I created a new branch to address this issue. I created a new key and tested it and it is writing files to the gh-pages branch. I'm not sure if something is happening when you try to pull it to the master?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Quansight/lsst_dashboard/issues/87?email_source=notifications&email_token=AAEJBFJJZAXXT6HRPBQMEBDQLAYUHA5CNFSM4IYXTGU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7JWTOA#issuecomment-533948856, or mute the thread https://github.com/notifications/unsubscribe-auth/AAEJBFJABHCODPLFZBQLAXTQLAYUHANCNFSM4IYXTGUQ .
@dharhas @ppwadhwa What's the status of this?
@kcpevey I assume we broke documentation when we moved to github actions?
Yes, closing in favor of https://github.com/Quansight/lsst_dashboard/issues/120
Looks like we may need to sort out the key stuff again.
See here: https://travis-ci.org/Quansight/lsst_dashboard/jobs/587496380