Skip to content

fix(docs): use correct public key name #316

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 6, 2019

Conversation

alexlafroscia
Copy link
Contributor

No description provided.

@alexlafroscia
Copy link
Contributor Author

Seems like Prettier fixed a bunch of formatting when I saved the file... Sorry about that.

I'm happy to fix the commit if want just the actual fix!

@@ -73,7 +74,7 @@ This will produce two files in your current directory: `deploy_key` (the private

On GitHub, open the page for your repo and navigate to _Settings_ -> _Deploy keys_ (or just directly visit <u>https://github.com/**[user]**/**[repo]**/settings/keys)</u> and click "Add deploy key".

Enter a name for your key and then paste the contents of your public key (`id_rsa.pub`) into the big textarea. Make sure you check the **Allow write access** box, then click "Add key" and you're all set.
Enter a name for your key and then paste the contents of your public key (`deploy_key.pub`) into the big textarea. Make sure you check the **Allow write access** box, then click "Add key" and you're all set.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm pretty sure you meant to reference the deployment key that was just created, not the default id_rsa key. This change makes it consistent with the documentation on ember-cli-deploy-git-ci

@dfreeman
Copy link
Contributor

dfreeman commented Feb 6, 2019

Thanks, @alexlafroscia!

@dfreeman dfreeman merged commit 89cf52d into ember-learn:master Feb 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants