<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>pull-request on Nelis&#39; blog</title>
    <link>https://nelis.boucke.be/tags/pull-request/</link>
    <description>Recent content in pull-request on Nelis&#39; blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Wed, 04 Oct 2017 00:00:00 +0000</lastBuildDate><atom:link href="https://nelis.boucke.be/tags/pull-request/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why and how do we use pull requests</title>
      <link>https://nelis.boucke.be/post/why-and-how-do-we-use-pull-request/</link>
      <pubDate>Wed, 04 Oct 2017 00:00:00 +0000</pubDate>
      
      <guid>https://nelis.boucke.be/post/why-and-how-do-we-use-pull-request/</guid>
      <description>The goal of this post is to share why teams I worked with used pull requests and how this was practically organized. Please note that I&amp;rsquo;m strongly in favor of using trunk-based development over pull requests, and I collected references to get you started in another post. But I still share experience, knowing it’s not a perfect example, as it might provide inspiration on the advantages and disadvantages of such an approach.</description>
    </item>
    
  </channel>
</rss>
