<?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 Georg Pauer</title>
    <link>/series/git/</link>
    <description>Recent content in git on Georg Pauer</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 30 Jan 2025 00:00:00 +0000</lastBuildDate><atom:link href="/series/git/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>more resources for learning and using git (2)</title>
      <link>/posts/learning-git-2/</link>
      <pubDate>Thu, 30 Jan 2025 00:00:00 +0000</pubDate>
      
      <guid>/posts/learning-git-2/</guid>
      <description>As a follow up to resources for learning git :
I totally missed, that oh my git has its own second level domain and a talk at FosDem 2021.
For the more seasoned user Oh Shit, Git!?! lists some quite common mishaps. A bit similar to this for GoLang.</description>
    </item>
    
    <item>
      <title>risks of embedded bare repositories</title>
      <link>/posts/embedded-bare-git-repositories/</link>
      <pubDate>Sun, 29 Oct 2023 00:00:00 +0000</pubDate>
      
      <guid>/posts/embedded-bare-git-repositories/</guid>
      <description>Have you ever wondered, why your IDE asks you, if you &amp;ldquo;trust&amp;rdquo; the code you checked out via git?
While the risks of embedded bare repositories is well described (more details here), I suspect that it will stay exploitable for quite some time.
There is an opt-in mitigation in setting safe.bareRepository to explicit with git 2.38.0. Also a proof of concept is available.
Just don&amp;rsquo;t forget the even more obvious risk with .</description>
    </item>
    
    <item>
      <title>resources for learning git</title>
      <link>/posts/learning-git/</link>
      <pubDate>Mon, 09 Jan 2023 00:00:00 +0000</pubDate>
      
      <guid>/posts/learning-git/</guid>
      <description>When someone wants to play a bit more with git: learngitbranching. If you afterwards want to rewrite history, watch the lets fck up history talk.
update I found the beautiful Oh my Git from bleeptrack and blinry, where you can try all that (low level) git operations in a Linux VM in your browser.</description>
    </item>
    
    <item>
      <title>reasons to master git cli</title>
      <link>/posts/master-git-on-cli/</link>
      <pubDate>Tue, 19 Apr 2022 00:00:00 +0000</pubDate>
      
      <guid>/posts/master-git-on-cli/</guid>
      <description>Five reasons to master git on the CLI</description>
    </item>
    
  </channel>
</rss>
