I think the current copy we have is a bit too indirect / wishy-washy! Ideally these sorts of important instuctional messgaes should be more assertive, but not too formal.
--
Unless your git repo is public, you must copy this ssh key to your repo settings, otherwise we won't be able to access the repo to deploy. Managing Deploy Keys on GitHub explains how to do it, just skip Step 1 and use this key:
For private Git repositories, you'll need to add this SSH key to your repo settings » (*) so Engine Yard can access and deploy your application:
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDBpDf138V3ksOF1rBQnkRpGihYxYUtqF1MktME4cj2af2yQkLzUT1h05BNBj8A2O3etvd4ESRyzwUQ3xazX3GwAsSgSoGd+djaRnoNsVKnFdeI9KXW0758e07oi2b2Q6Ycw/WAT6JDuT4wpkuGqtLggvQbkHoG/MLyRSbp29nvwYheWKl5gtZl2yIpQPoxf83b5MKqtIKW/puZz1XdiOU1cY5LIkvYTHNiliCfm2ZuFGMNoTjNFTsvmJsuUHHTas/UKbU1wgJ1l46Jmyt/X/kOemaj5cVpjOambkDRqZQ3wy7Hnx0dRdIEOrrNguN/3fBYs7f0nkZ8cmcOcGlEdA23 deploy@engineyard
See Managing Deploy Keys » for further explanation.
--
(*) Note: Seeing as we already have the Git repo URI that they're deploying for that app, is there any way we could smartly render the link in the instructional copy to take them directly to their https://github.com/ACCOUNT/REPO/settings/keys page, rather than detailing a series of steps (go to your repo, click settings, click deploy keys).
Sounds good to me.
Re: repo settings, I don't see why not. Good idea.