-
Notifications
You must be signed in to change notification settings - Fork 59.8k
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
Multiple deploy keys #501
Multiple deploy keys #501
Conversation
Adds instructions on defining unique ssh keys (deploy keys) per repo on one server by using the ssh config file.
Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
Thanks for opening a PR @tarrenj! I'll get this triaged for review ✨ |
Fixes a small typo
Found and fixed a small typo, sorry if this bounces it back into Triage! |
@tarrenj - thanks so much for creating this PR! 🎉 I've added some small edits to the draft, just to suit our existing docs conventions. Could you check that you're happy with my suggestions? 👍 You can find the rendered preview here: https://docs-501--multiple-deploy-keys.herokuapp.com/en/free-pro-team@latest/developers/overview/managing-deploy-keys#using-multiple-repositories-on-one-server |
They look good to me! I used this existing page as a reference, so that's another discrepancy for you guys to be aware of. |
Checked with the folks from support, and they're happy with this draft 🎉 |
Now doing some readiness checks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some versioning for the different page versions is probably needed, plus a few suggestions to clarify the behavior.
Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com>
Adds instructions on defining unique ssh keys (deploy keys) per repo on one server by using the ssh config file.
Why:
#500
What's being changed:
Check off the following: