<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>devops on GeekTrainer</title>
    <link>https://geektrainer.dev/tags/devops/</link>
    <description>Recent content in devops on GeekTrainer</description>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Wed, 23 Nov 2022 00:00:00 +0000</lastBuildDate><atom:link href="https://geektrainer.dev/tags/devops/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>New tools won&#39;t change old culture</title>
      <link>https://geektrainer.dev/code/devops-culture/</link>
      <pubDate>Wed, 23 Nov 2022 00:00:00 +0000</pubDate>
      
      <guid>https://geektrainer.dev/code/devops-culture/</guid>
      <description>I don&amp;rsquo;t know who needs to hear this, but buying a new treadmill won&amp;rsquo;t make you a runner.
It&amp;rsquo;s a mistake we&amp;rsquo;ve all made at some point. We&amp;rsquo;ve all decided, &amp;ldquo;This is the year! I&amp;rsquo;m going to spend lots of money on new equipment, on gear, on clothes, on cool shoes, and I&amp;rsquo;m going to &amp;lt;fill in the blank here&amp;gt;&amp;rdquo;. And we&amp;rsquo;ve all been rather disappointed when said shiny items find themselves collecting dust, and the treadmill/rower/elliptical are expensive clothing racks.</description>
    </item>
    
    <item>
      <title>Streamlining pull request reviews with suggestions</title>
      <link>https://geektrainer.dev/code/suggestions-pr/</link>
      <pubDate>Mon, 29 Aug 2022 00:00:00 +0000</pubDate>
      
      <guid>https://geektrainer.dev/code/suggestions-pr/</guid>
      <description>We&amp;rsquo;ve all been there. We&amp;rsquo;re reviewing someone&amp;rsquo;s code in a pull request (PR) and we spot a small mistake. A typo. The wrong option was set. A boolean flag was reversed. Something simple. What&amp;rsquo;s the best way to suggest a fix?
One way is to create new branch and PR into the one you&amp;rsquo;re reviewing. Seems like a bit too much work, and maybe a little too formal.
For a repository where you have permissions, you could simply push the updates.</description>
    </item>
    
  </channel>
</rss>
