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 wish to always use the SSH protocol for every project. I am using an SSH key that is set in the user's home directory at ~/.ssh/ that allows git to clone from GitHub; authentication like this seems reasonable and works correctly.
Could it perhaps be possible to add another check here for some application level config that forces us to the SSH protocol regardless of project level settings?
Another option here could be to use the Git build type instead. The downside of this method, is we then lose the ability to get build updates in Github from php-censor. This is not ideal as it would be preferred to have all the features of the GithubBuild regardless of the authentication or cloning method.
I wish to always use the SSH protocol for every project. I am using an SSH key that is set in the user's home directory at
~/.ssh/that allows git to clone from GitHub; authentication like this seems reasonable and works correctly.However, because of the check in the
GithubBuild.phpclass https://github.com/php-censor/php-censor/blob/master/src/Model/Build/GithubBuild.php#L173, HTTP will be forced when there's no private key present at the project level.Could it perhaps be possible to add another check here for some application level config that forces us to the SSH protocol regardless of project level settings?
Another option here could be to use the Git build type instead. The downside of this method, is we then lose the ability to get build updates in Github from php-censor. This is not ideal as it would be preferred to have all the features of the GithubBuild regardless of the authentication or cloning method.