Skip to content

ci: remove no longer used (?) github repo deploy key (to push to gh-pages branch?)#485

Merged
jcrist merged 1 commit intodask:mainfrom
consideRatio:pr/remove-outdated-deployment-key
Mar 1, 2022
Merged

ci: remove no longer used (?) github repo deploy key (to push to gh-pages branch?)#485
jcrist merged 1 commit intodask:mainfrom
consideRatio:pr/remove-outdated-deployment-key

Conversation

@consideRatio
Copy link
Collaborator

I'm not sure, but I think this repo has a deployment key that has been used when used together with TravisCI as a means for TravisCI to push back updates to the gh-pages branch of this repo.

It was added as part of #107, I think perhaps it was outdated even at that time as I found no reference to the filename in the repo, and I saw that the TravisCI had an environment variable that probably was used to help provide credentials to a utility pushing built docs to the gh-pages branch.

If it is a deployment key for this repo, as indicated by the filename github_deploy_key_dask_dask_gateway.enc, it should be registered at https://github.com/dask/dask-gateway/settings/keys. It should reasonably be cleared from there as well.

@martindurant
Copy link
Member

I can confirm that there are no registered keys for this repo.

@jcrist
Copy link
Member

jcrist commented Mar 1, 2022

This is left over from using doctr to publish docs on travis ci, perfectly fine to delete it now.

@jcrist jcrist merged commit 7c91059 into dask:main Mar 1, 2022
@consideRatio consideRatio changed the title Remove no longer used (?) github repo deploy key (to push to gh-pages branch?) ci: remove no longer used (?) github repo deploy key (to push to gh-pages branch?) Apr 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants