<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Git on AD Blogdown</title><link>https://ad.vgiscience.org/links/tags/git/</link><description>Recent content in Git on AD Blogdown</description><generator>Hugo</generator><language>en-US</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Sun, 19 Apr 2026 08:23:41 +0200</lastBuildDate><atom:link href="https://ad.vgiscience.org/links/tags/git/index.xml" rel="self" type="application/rss+xml"/><item><title>GitLab Deploy Keys instead of Access Tokens</title><link>https://ad.vgiscience.org/links/posts/2026-04-19_gitlab_deploy_keys/</link><pubDate>Sun, 19 Apr 2026 00:07:35 +0000</pubDate><guid>https://ad.vgiscience.org/links/posts/2026-04-19_gitlab_deploy_keys/</guid><description>I manage a large number of Git repositories across many nested Linux user environments running in rootless namespaces and container-like setups. Access to these environments is done via (e.g.)sudo machinectl shell codimd@ under restricted user contexts, which makes standard SSH workflows such as SSH agent forwarding unreliable or not possible at all.
As a result, maintaining access to Git remotes for frequent pushes becomes quite cumbersome. So far, I relied on personal access tokens hardcoded in HTTPS git origin URLs.</description></item></channel></rss>