<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Feature-Based-Work on Scholion</title><link>https://scholion.thluiz.com/tags/feature-based-work/</link><description>Recent content in Feature-Based-Work on Scholion</description><generator>Hugo -- gohugo.io</generator><language>pt-BR</language><copyright>© 2026</copyright><lastBuildDate>Tue, 07 Mar 2017 21:44:56 -0300</lastBuildDate><atom:link href="https://scholion.thluiz.com/tags/feature-based-work/index.xml" rel="self" type="application/rss+xml"/><item><title>When to make a Git Commit</title><link>https://scholion.thluiz.com/notes/when-to-make-a-git-commit/</link><pubDate>Tue, 07 Mar 2017 21:44:56 -0300</pubDate><guid>https://scholion.thluiz.com/notes/when-to-make-a-git-commit/</guid><description>The post says to commit when you finish a unit of work or when you have changes you may want to undo. It argues that units of work should be defined by feature, not by time or file type.</description></item></channel></rss>