Include check to verify user has git clone SSH access as prerequisite.

[a-t-0]

Currently, deleting all SSH credentials, rebooting and cloning, e.g.:

git clone git@github.com:a-t-0/gitlab-ci-build-statuses.git

Yields:

Cloning into 'gitlab-ci-build-statuses'...
The authenticity of host 'github.com (140.82.121.4)' can't be established.
ED25519 key fingerprint is SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU.
This key is not known by any other names
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added 'github.com' (ED25519) to the list of known hosts.
git@github.com: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

This prevents the function that sets the GitHub SSH deploy key from working properly. This is because that function clones the the gitlab-ci-build-statuses repository a few times for testing purposes.

[a-t-0]

It is not required for setting the GitHub SSH deploy key, however, it may be used for other cases. This can be resolved by :

• [ ] creating a method:

  clone_github_repo(){}
  which first tries to clone using ssh, and if that not works, clones with https.

• [ ] Also, you should identify where GitHub push access is required, and if yes, verify an SSH deploy key is set for those scenarios.

[a-t-0]

Check if the user has GitHub SSH access before starting as prerequisite check.

[a-t-0]

Completed by creating a basic GitHub SSH access check in the prerequisites.