What is a summary of your change?
The current document provides both approaches(http and ssh) for users to clone the repository.
However, based on some recent new-user experience it was found that users get an error while pushing changes when ssh method is not used.
Change is based out of this suggestion
Why is this change helpful?
This new change suggests that ssh is the recommended way to go forward when cloning the repository for the setup.
This will prevent future new-users to avoid the current issue faced.
Any specific details to consider?
These can also be updated on the other docs as well.
What do you think is the outcome of this change?
The user, on initial steps itself, will use ssh approach with the repository, and will be able to execute tasks(push/pull) successfully.
What is a summary of your change?
The current document provides both approaches(
httpandssh) for users to clone the repository.However, based on some recent new-user experience it was found that users get an error while pushing changes when
sshmethod is not used.Change is based out of this suggestion
Why is this change helpful?
This new change suggests that
sshis the recommended way to go forward when cloning the repository for the setup.This will prevent future new-users to avoid the current issue faced.
Any specific details to consider?
These can also be updated on the other docs as well.
What do you think is the outcome of this change?
The user, on initial steps itself, will use
sshapproach with the repository, and will be able to execute tasks(push/pull) successfully.