<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://wiki.pushmindstack.com/lib/exe/css.php?s=feed" type="text/css"?>
<rss version="2.0">
    <channel xmlns:g="http://base.google.com/ns/1.0">
        <title>PushMindStack - tools:git:tips</title>
        <description></description>
        <link>https://wiki.pushmindstack.com/</link>
        <lastBuildDate>Wed, 15 Apr 2026 23:41:38 +0000</lastBuildDate>
        <generator>FeedCreator 1.8</generator>
        <image>
            <url>https://wiki.pushmindstack.com/_media/wiki/dokuwiki.svg</url>
            <title>PushMindStack</title>
            <link>https://wiki.pushmindstack.com/</link>
        </image>
        <item>
            <title>Modify a commit which has been pushed</title>
            <link>https://wiki.pushmindstack.com/tools/git/tips/230510</link>
            <description>Modify a commit which has been pushed

Steps

	*  Find the ID (denoted by pre-cmt-id) of the previous commit of the commit that you need to modify.
	*  Run git rebase -i pre-cmt-id.
	*  Modify pick to edit in the line where the commit to be modified is located. Then save and exit.</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Sun, 10 Mar 2024 17:18:27 +0000</pubDate>
        </item>
        <item>
            <title>Push only one specified commit</title>
            <link>https://wiki.pushmindstack.com/tools/git/tips/230512</link>
            <description>Push only one specified commit

Steps

	*  Run git log --oneline to list the commit (push-cmt) to be pushed and the SHA (rmt-head-sha) of the HEAD (rmt-head) of the remote repository.
	*  Run git rebase -i rmt-head-sha to re-order the push-cmt to follow the</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Thu, 07 Mar 2024 16:12:37 +0000</pubDate>
        </item>
        <item>
            <title>Git branch topography</title>
            <link>https://wiki.pushmindstack.com/tools/git/tips/branch_topo</link>
            <description>Git branch topography

Steps

Append the following code to ~/.gitconfig. Then you can run 
git lg, git lg1, git lg2 and
git lg3 to see the output, respectively.



Further Reading

	*  &lt;https://stackoverflow.com/questions/1838873/visualizing-branch-topology-in-git/34467298#34467298&gt;</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Sun, 10 Mar 2024 17:18:33 +0000</pubDate>
        </item>
        <item>
            <title>Revert to a Specific Commit</title>
            <link>https://wiki.pushmindstack.com/tools/git/tips/revert_amend</link>
            <description>Revert to a Specific Commit

Steps

	*  Run git reflog to see the reference logsReference logs, or reflogs, record when the tips of branches and other references were updated in the local repository. .
	*  Run git reset --soft HEAD@{id}, where id is the ID of target commit to revert to.</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Sun, 10 Mar 2024 17:12:54 +0000</pubDate>
        </item>
    </channel>
</rss>
