<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Github on Personal Blog of Maximilian Ehlers</title><link>https://blog.sodawa.com/tags/github/</link><description>Recent content in Github on Personal Blog of Maximilian Ehlers</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Mon, 17 Aug 2020 19:42:42 +0200</lastBuildDate><atom:link href="https://blog.sodawa.com/tags/github/index.xml" rel="self" type="application/rss+xml"/><item><title>Using private git submodules in GitHub CI</title><link>https://blog.sodawa.com/blog/private-submodules-in-github-ci/</link><pubDate>Mon, 17 Aug 2020 19:42:42 +0200</pubDate><guid>https://blog.sodawa.com/blog/private-submodules-in-github-ci/</guid><description>Do you need to use submodules in your project? Do you use GitHub CI to build your project in the Cloud automatically?
If so then this article will help you to do this safely and without creating additional users or adding Tokens with a wide permission set. The idea is to use deploy keys that have read-only permissions.
The quick rundown for all you experts:
create SSH keypair on your computer add public part as deploy key to private submodule add private key as secret in repo where action is triggered.</description></item></channel></rss>