<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://dokuwiki.hampel-soft.com/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://dokuwiki.hampel-soft.com/feed.php">
        <title>HAMPEL SOFTWARE ENGINEERING kb:bestpractices:scc</title>
        <description></description>
        <link>https://dokuwiki.hampel-soft.com/</link>
        <image rdf:resource="https://dokuwiki.hampel-soft.com/lib/tpl/dokuwiki/images/favicon.ico" />
       <dc:date>2026-09-17T14:00:56+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://dokuwiki.hampel-soft.com/kb/bestpractices/scc/fork?rev=1752073600&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.hampel-soft.com/kb/bestpractices/scc/gitflow-workflow?rev=1771611578&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.hampel-soft.com/kb/bestpractices/scc/project-forking-workflow?rev=1665004348&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.hampel-soft.com/kb/bestpractices/scc/rules?rev=1780907093&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.hampel-soft.com/kb/bestpractices/scc/smartgit?rev=1734459327&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.hampel-soft.com/kb/bestpractices/scc/sourcetree?rev=1734472747&amp;do=diff"/>
                <rdf:li rdf:resource="https://dokuwiki.hampel-soft.com/kb/bestpractices/scc/workflow?rev=1660326577&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://dokuwiki.hampel-soft.com/lib/tpl/dokuwiki/images/favicon.ico">
        <title>HAMPEL SOFTWARE ENGINEERING</title>
        <link>https://dokuwiki.hampel-soft.com/</link>
        <url>https://dokuwiki.hampel-soft.com/lib/tpl/dokuwiki/images/favicon.ico</url>
    </image>
    <item rdf:about="https://dokuwiki.hampel-soft.com/kb/bestpractices/scc/fork?rev=1752073600&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-07-09T15:06:40+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>13 Fork Setup</title>
        <link>https://dokuwiki.hampel-soft.com/kb/bestpractices/scc/fork?rev=1752073600&amp;do=diff</link>
        <description>13 Fork Setup

Here at HSE, we all agree that Git Fork is our preferred graphical git client. It is developed and maintained by two very responsive developers who are making a living providing this fantastic tool. With its robustness, feature completeness and ease of use, it is worth every single cent!</description>
    </item>
    <item rdf:about="https://dokuwiki.hampel-soft.com/kb/bestpractices/scc/gitflow-workflow?rev=1771611578&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-02-20T18:19:38+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>11 Gitflow Workflow</title>
        <link>https://dokuwiki.hampel-soft.com/kb/bestpractices/scc/gitflow-workflow?rev=1771611578&amp;do=diff</link>
        <description>11 Gitflow Workflow

See the Gitflow page for more information about the workflow itself.

HSE Specifics
  Each developer should work on no more than one feature branch at any timeCreate meaningful feature branch names and add your name (or initials) to the branch for easy identification - see</description>
    </item>
    <item rdf:about="https://dokuwiki.hampel-soft.com/kb/bestpractices/scc/project-forking-workflow?rev=1665004348&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-10-05T21:12:28+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>12 Project Forking Workflow</title>
        <link>https://dokuwiki.hampel-soft.com/kb/bestpractices/scc/project-forking-workflow?rev=1665004348&amp;do=diff</link>
        <description>12 Project Forking Workflow

See the Project Forking page for more information about the workflow itself.</description>
    </item>
    <item rdf:about="https://dokuwiki.hampel-soft.com/kb/bestpractices/scc/rules?rev=1780907093&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-06-08T08:24:53+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>01 Rules &amp; Guides</title>
        <link>https://dokuwiki.hampel-soft.com/kb/bestpractices/scc/rules?rev=1780907093&amp;do=diff</link>
        <description>01 Rules &amp; Guides

These rules and guides are written with git (a decentralised SCC system) in mind: 

- commit = add changes to local repository 

- push = sync changes with remote (central) repository 

Common
Commit early, commit oftenCommit only intentional changes (avoid “Save all”!)</description>
    </item>
    <item rdf:about="https://dokuwiki.hampel-soft.com/kb/bestpractices/scc/smartgit?rev=1734459327&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-12-17T18:15:27+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>14 Smartgit Setup</title>
        <link>https://dokuwiki.hampel-soft.com/kb/bestpractices/scc/smartgit?rev=1734459327&amp;do=diff</link>
        <description>14 Smartgit Setup

Git settings in general can be saved on different levels. Sometimes it may be handy to develop on a shared machine and the repository is stored for common access under C:\Users\Public\Documents\Bitbucket. In this case, user settings are not allowed to be stored inside the repo. Otherwise, one developer could commit with the name of another developer. To prevent this, make sure that</description>
    </item>
    <item rdf:about="https://dokuwiki.hampel-soft.com/kb/bestpractices/scc/sourcetree?rev=1734472747&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-12-17T21:59:07+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>15 Sourcetree</title>
        <link>https://dokuwiki.hampel-soft.com/kb/bestpractices/scc/sourcetree?rev=1734472747&amp;do=diff</link>
        <description>15 Sourcetree

LV Compare

To use LV Compare in Sourcetree, adjust the settings under Tools -&gt; Options in the Diff tab under External Diff/Merge. Configure these values:
External Diff Tool       Custom       Diff Command             see below        Arguments</description>
    </item>
    <item rdf:about="https://dokuwiki.hampel-soft.com/kb/bestpractices/scc/workflow?rev=1660326577&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-08-12T17:49:37+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>10 Workflow</title>
        <link>https://dokuwiki.hampel-soft.com/kb/bestpractices/scc/workflow?rev=1660326577&amp;do=diff</link>
        <description>10 Workflow

We use the Gitflow workflow for our customer projects (everybody has write access to the repositories). 

We use the Project Forking workflow for our open-source projects (contributors do not have write access to those repositories).

There is an abundance of workflows for git, here are some starting points:</description>
    </item>
</rdf:RDF>
