You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to use this in an environment with travis. There are two common options authentication there, one being a github personal access token, the other to use a project specific deployment ssh key. Both are read via the environment, the ssh key is usually base64 encoded.
I'm not totally sure ssh key via env works, I've read reports that the travis environment variables are too short for a full ssh key, but from a simple test it seemed to work for me.
What do you think about adding support for this to grunt-gh-pages? I'd imagine something like this in the config:
In the first case, it would read that key, base64-decode it, write it to a temporary file, call ssh-add on it. In the second case, it would parse the repo url and add the token as a username, e.g. https://tokenFromEnvHere@github.com/tschaub/grunt-gh-pages.git. If you prefer, we could use a single config key envAuth and then detect if its a https repo url or ssh url.
If you are up for this, I could probably find some time to send a pull request. On the other hand, this can of course be done with a custom task that runs beforehand and sets the right config values.
The text was updated successfully, but these errors were encountered:
I'd like to use this in an environment with travis. There are two common options authentication there, one being a github personal access token, the other to use a project specific deployment ssh key. Both are read via the environment, the ssh key is usually base64 encoded.
I'm not totally sure ssh key via env works, I've read reports that the travis environment variables are too short for a full ssh key, but from a simple test it seemed to work for me.
What do you think about adding support for this to grunt-gh-pages? I'd imagine something like this in the config:
In the first case, it would read that key, base64-decode it, write it to a temporary file, call ssh-add on it. In the second case, it would parse the repo url and add the token as a username, e.g.
https://tokenFromEnvHere@github.com/tschaub/grunt-gh-pages.git
. If you prefer, we could use a single config keyenvAuth
and then detect if its a https repo url or ssh url.If you are up for this, I could probably find some time to send a pull request. On the other hand, this can of course be done with a custom task that runs beforehand and sets the right config values.
The text was updated successfully, but these errors were encountered: