id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
33585	lacking hint to SSH setup (Working with Git and GitHub)	Samuel Hartmann	Carlton Gibson	"Starting to work on #33544 I found the following:

The explanation [https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/working-with-git/#setting-up-local-repository ""Setting up local repository""] in ""Working with Git and GitHub"" quitely assumes that people have already set up their local Git and GitHub for use of SSH.

They say:
> You should also set up django/django as an “upstream” remote (that is, tell git that the reference Django repository was the source of your fork of it):
>
> 
> {{{
> git remote add upstream git@github.com:django/django.git
> git fetch upstream
> }}}

I didn't set up SSH before.
Hence I got the following error when running `git fetch upstream`:
{{{
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.
}}}

The reason and solution for that error are described in [https://stackoverflow.com/a/12940681 this stackoverflow reply].
Basically you need to set up an SSH key on your local machine and add it to your GitHub profile.
This enables you to [https://docs.github.com/en/authentication/connecting-to-github-with-ssh connect to GitHub].

I suggest two possible solutions:
1. insert a new section after the [https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/working-with-git/#installing-git Installing Git] section
2. change the SSH notations (like git@^^github.com:django/django.git) to HTTPS notations (like https://github.com/django/django.git) instead

If the second approach makes sense, I'd prefer this one because it's easier to understand and needs less effort from a setup perspective.
Hence simplifies the start for first time contributers."	Bug	closed	Documentation	dev	Normal	fixed	documentation, git, github contributing, contribution		Ready for checkin	1	0	0	0	1	0