<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://wiki.evergreen-ils.org/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://wiki.evergreen-ils.org/feed.php">
        <title>Evergreen DokuWiki - newdevs:git</title>
        <description></description>
        <link>https://wiki.evergreen-ils.org/</link>
        <image rdf:resource="https://wiki.evergreen-ils.org/lib/exe/fetch.php?media=wiki:logo.svg" />
       <dc:date>2026-05-03T15:00:22+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://wiki.evergreen-ils.org/doku.php?id=newdevs:git:commands&amp;rev=1753333933&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.evergreen-ils.org/doku.php?id=newdevs:git:create&amp;rev=1737045444&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.evergreen-ils.org/doku.php?id=newdevs:git:install&amp;rev=1702497794&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.evergreen-ils.org/doku.php?id=newdevs:git:signoff&amp;rev=1722260324&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.evergreen-ils.org/doku.php?id=newdevs:git:test&amp;rev=1685635092&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://wiki.evergreen-ils.org/lib/exe/fetch.php?media=wiki:logo.svg">
        <title>Evergreen DokuWiki</title>
        <link>https://wiki.evergreen-ils.org/</link>
        <url>https://wiki.evergreen-ils.org/lib/exe/fetch.php?media=wiki:logo.svg</url>
    </image>
    <item rdf:about="https://wiki.evergreen-ils.org/doku.php?id=newdevs:git:commands&amp;rev=1753333933&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-07-24T05:12:13+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>commands</title>
        <link>https://wiki.evergreen-ils.org/doku.php?id=newdevs:git:commands&amp;rev=1753333933&amp;do=diff</link>
        <description>New Developers Working Group

Useful Git Commands

	*  git add myfile.txt --&gt; stage a specific file
	*  git add -A --&gt; stage all modified files in the current directory and subdirectories
	*  git add . --&gt; (Note the period) stage all modified files in the current directory but not subdirectories</description>
    </item>
    <item rdf:about="https://wiki.evergreen-ils.org/doku.php?id=newdevs:git:create&amp;rev=1737045444&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-01-16T16:37:24+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>create</title>
        <link>https://wiki.evergreen-ils.org/doku.php?id=newdevs:git:create&amp;rev=1737045444&amp;do=diff</link>
        <description>New Developers Working Group

Git for Windows

Using Git to Create New Branches

When you make code changes that you wish to post for review, you will create a git branch to store them in.

1. Update Your Local Repository

	*  Open Git Bash
	*  Navigate into your Evergreen repository</description>
    </item>
    <item rdf:about="https://wiki.evergreen-ils.org/doku.php?id=newdevs:git:install&amp;rev=1702497794&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-12-13T20:03:14+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>install</title>
        <link>https://wiki.evergreen-ils.org/doku.php?id=newdevs:git:install&amp;rev=1702497794&amp;do=diff</link>
        <description>New Developers Working Group

Git for Windows

If you are running Evergreen on an Ubuntu virtual machine, git should already be installed, but this will allow you to code on a Windows machine without a virtual machine. The git commands will be the same regardless of the environment.</description>
    </item>
    <item rdf:about="https://wiki.evergreen-ils.org/doku.php?id=newdevs:git:signoff&amp;rev=1722260324&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-07-29T13:38:44+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>signoff</title>
        <link>https://wiki.evergreen-ils.org/doku.php?id=newdevs:git:signoff&amp;rev=1722260324&amp;do=diff</link>
        <description>New Developers Working Group

Git for Windows

How to Sign Off on a Branch

These instructions are the same regardless of whether you have tested this on your own test server or on a remote test server that has been set up for bug squashing.

After you have successfully tested a branch that someone else has created and see that it is working well, you will create a sign-off branch to acknowledge that you have tested it.</description>
    </item>
    <item rdf:about="https://wiki.evergreen-ils.org/doku.php?id=newdevs:git:test&amp;rev=1685635092&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-06-01T15:58:12+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>test</title>
        <link>https://wiki.evergreen-ils.org/doku.php?id=newdevs:git:test&amp;rev=1685635092&amp;do=diff</link>
        <description>New Developers Working Group

Git for Windows

Using Git to Test Patches

1. Get the Commit Hash

First, you will need to identify the unique commit ID (hash) of the patch you wish to test. This is most easily found by clicking on a link in the related launchpad bug. Once  there, copy the first 7+ characters from the unique commit code.</description>
    </item>
</rdf:RDF>
