<?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 iMil.net</title>
    <link>http://imil.net/blog/tags/git/</link>
    <description>Recent content in Git on iMil.net</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 01 May 2020 16:25:17 +0200</lastBuildDate>
    <atom:link href="http://imil.net/blog/tags/git/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Publish Binary Releases on Gitlab</title>
      <link>http://imil.net/blog/posts/2020/binary-releases-on-gitlab/</link>
      <pubDate>Fri, 01 May 2020 16:25:17 +0200</pubDate>
      <guid>http://imil.net/blog/posts/2020/binary-releases-on-gitlab/</guid>
      <description>&lt;p&gt;I switched to &lt;a href=&#34;https://gitlab.com&#34;&gt;Gitlab&lt;/a&gt; when &lt;em&gt;Github&lt;/em&gt; was bought by &lt;em&gt;Microsoft&lt;/em&gt;. Call me extremist, stupid, and all the names you like, I personally felt the need to do it.&lt;br&gt;&#xA;And quite honestly, I&amp;rsquo;m pretty happy with that choice, &lt;em&gt;Gitlab&lt;/em&gt; is an incredibly useful suite, we use the community version at work and would never go back. But there&amp;rsquo;s one thing that&amp;rsquo;s pretty annoying with &lt;em&gt;Gitlab&lt;/em&gt;, their documentation organization. Honestly it&amp;rsquo;s like they &lt;strong&gt;don&amp;rsquo;t&lt;/strong&gt; want you to figure out how to do things. It&amp;rsquo;s often split into tens of various links and you end up reading issues discussions without really knowing if the feature you&amp;rsquo;d like is implemented or just an idea at that point.&lt;/p&gt;</description>
    </item>
    <item>
      <title>From GitLab CI to Docker Hub</title>
      <link>http://imil.net/blog/posts/2018/from-gitlab-ci-to-docker-hub/</link>
      <pubDate>Sun, 04 Nov 2018 09:24:59 +0000</pubDate>
      <guid>http://imil.net/blog/posts/2018/from-gitlab-ci-to-docker-hub/</guid>
      <description>&lt;p&gt;With all the noise around those topics I would have imagined this one had been covered thousands of time, yet I did not find a single complete resource on this subject which I found to be a basic building block: pushing docker images from &lt;a href=&#34;https://about.gitlab.com/product/continuous-integration/&#34;&gt;GitLab CI&lt;/a&gt; to the &lt;a href=&#34;https://hub.docker.com/&#34;&gt;Docker Hub registry&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;There&amp;rsquo;s actually an opened issue on &lt;a href=&#34;https://github.com/docker/hub-feedback/issues/334&#34;&gt;Docker GitHub&lt;/a&gt;&amp;rsquo;s that&amp;rsquo;s sitting there for 3 years, and it really feels more like a political / strategic / commercial issue than a technical one. Point being, there&amp;rsquo;s no straightforward integration between &lt;em&gt;GitLab.com&lt;/em&gt; and &lt;em&gt;Docker Hub&lt;/em&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
