<?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 ✨</title><link>/tags/git/</link><description>Recent content in git on ✨</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sun, 04 Aug 2019 10:21:07 -0400</lastBuildDate><atom:link href="/tags/git/index.xml" rel="self" type="application/rss+xml"/><item><title>Work-In-Progress (WIP) commits: a git technique in Trunk-Based Development</title><link>/post/trunk-dev-wip-commits/</link><pubDate>Sun, 04 Aug 2019 10:21:07 -0400</pubDate><guid>/post/trunk-dev-wip-commits/</guid><description>When building a software product on a team, to create an effective and sustainable development flow, one needs to abide by a version control branching model that is agreed upon all team members. If there is a chosen approach to branching, individual contributors on a team can contribute code without issue.
In this post, I want to focus on a specific technique within a specific branching model that I believe is quite effective at keeping each contributor productive without introducing cognitive overhead of a complex branching model.</description></item></channel></rss>