<?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 Sascha Willems</title>
    <link>https://www.saschawillems.de/tags/git/</link>
    <description>Recent content in git on Sascha Willems</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>de-de</language>
    <managingEditor>webmaster@saschawillems.de (www.saschawillems.de)</managingEditor>
    <webMaster>webmaster@saschawillems.de (www.saschawillems.de)</webMaster>
    <lastBuildDate>Sun, 10 Sep 2017 12:41:13 +0000</lastBuildDate><atom:link href="https://www.saschawillems.de/tags/git/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to shrink down a git(hub) repository</title>
      <link>https://www.saschawillems.de/blog/2017/09/10/how-to-shrink-down-a-github-repository/</link>
      <pubDate>Sun, 10 Sep 2017 12:41:13 +0000</pubDate>
      <author>webmaster@saschawillems.de (www.saschawillems.de)</author>
      <guid>https://www.saschawillems.de/blog/2017/09/10/how-to-shrink-down-a-github-repository/</guid>
      <description>Starting point With my Vulkan C++ example github repository approaching 200 MB in size I decided it was about time to shrink it down to a reasonable size again. Shrinking a git(hub) repository isn&amp;rsquo;t just about deleting locally present files but requires cleaning up the history as files that have been removed are still present in the repository&amp;rsquo;s history and therefore still contribute to it&amp;rsquo;s size.
A big chunk of the repo&amp;rsquo;s size is caused by binary assets like textures and 3d models.</description>
    </item>
    
  </channel>
</rss>
