<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Revision on Micha Kops&#39; Tech Notes</title>
    <link>https://www.hascode.com/tags/revision/</link>
    <description>Recent content in Revision on Micha Kops&#39; Tech Notes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>Copyright © 2010 - 2025 Micha Kops. #e9d956c0c0154a221ad83c925346a8fa0e72f866</copyright>
    <lastBuildDate>Sun, 16 Dec 2012 00:00:00 +0100</lastBuildDate>
    <atom:link href="https://www.hascode.com/tags/revision/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Creating Pre-Commit-Hooks in Git and Mercurial: Prefix Commit Messages for Feature/Story Branches</title>
      <link>https://www.hascode.com/creating-pre-commit-hooks-in-git-and-mercurial-prefix-commit-messages-for-feature/story-branches/</link>
      <pubDate>Sun, 16 Dec 2012 00:00:00 +0100</pubDate>
      <guid>https://www.hascode.com/creating-pre-commit-hooks-in-git-and-mercurial-prefix-commit-messages-for-feature/story-branches/</guid>
      <description>&lt;div id=&#34;preamble&#34;&gt;
&lt;div class=&#34;sectionbody&#34;&gt;
&lt;div class=&#34;paragraph&#34;&gt;
&lt;p&gt;Managing my projects’ source code I am using Git also as Mercurial. Therefore I often encounter the situation where I am creating a special branch to implement a specific user story or feature request.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&#34;paragraph&#34;&gt;
&lt;p&gt;Now when working on such a story branch I often enter the issue-key or a short title as a prefix for each commit message. Doing this by manually is a waste of time and error-prone and luckily for us, each of both DVCS offers us an easy API to add custom hooks to the different life-cycle events.&lt;/p&gt;
&lt;/div&gt;</description>
    </item>
  </channel>
</rss>
