|
@@ -8,12 +8,12 @@
|
|
|
<language>en-us</language>
|
|
|
<managingEditor>me@codeskraps.com (codeskraps)</managingEditor>
|
|
|
<webMaster>me@codeskraps.com (codeskraps)</webMaster>
|
|
|
- <lastBuildDate>Mon, 15 Apr 2024 16:56:53 +0200</lastBuildDate>
|
|
|
+ <lastBuildDate>Wed, 17 Apr 2024 16:56:53 +0200</lastBuildDate>
|
|
|
<atom:link href="https://codeskraps.com/tags/ssh/index.xml" rel="self" type="application/rss+xml" />
|
|
|
<item>
|
|
|
<title>Configuring SSH Keys for Individual Git Commands</title>
|
|
|
<link>https://codeskraps.com/posts/2024/git_ssh_command/</link>
|
|
|
- <pubDate>Mon, 15 Apr 2024 16:56:53 +0200</pubDate><author>me@codeskraps.com (codeskraps)</author>
|
|
|
+ <pubDate>Wed, 17 Apr 2024 16:56:53 +0200</pubDate><author>me@codeskraps.com (codeskraps)</author>
|
|
|
<guid>https://codeskraps.com/posts/2024/git_ssh_command/</guid>
|
|
|
<description><p>When working with Git repositories, you often need to authenticate using SSH keys. While you can configure SSH settings globally, there are times when you need to use a specific SSH key for just one command. This is particularly useful when cloning a new repository or adding a submodule, where there isn&rsquo;t yet a local <code>.git/config</code> file to modify.</p></description>
|
|
|
</item>
|