<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Reset on 每日拍拍</title>
    <link>https://dailypypy.org/tags/reset/</link>
    <description>Recent content in Reset on 每日拍拍</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>zh-tw</language>
    <copyright>© 2026 每日拍拍</copyright>
    <lastBuildDate>Sat, 19 Sep 2026 10:54:00 +0800</lastBuildDate><atom:link href="https://dailypypy.org/tags/reset/index.xml" rel="self" type="application/rss+xml" />
    <follow_challenge>
      <feedId>155076163427069952</feedId>
      <userId>154825760438254592</userId>
    </follow_challenge>
    
    
    <item>
      <title>Git reset、restore、revert 實戰：選對復原工具</title>
      <link>https://dailypypy.org/learn/git-reset-restore-revert/</link>
      <pubDate>Sat, 19 Sep 2026 10:54:00 +0800</pubDate>
      
      <guid>https://dailypypy.org/learn/git-reset-restore-revert/</guid>
      <description>&lt;!---
1440x768
prompt: masterpiece, best quality, highres, clean anime illustration, japanese anime style, soft shading, flat color design, 1girl, black hair, green eyes, white off-shoulder shirt, black short skirt, close-up portrait, slight side profile, looking over shoulder, calm reassuring smile, looking at viewer, pastel periwinkle blue and soft coral background, subtle three-layer translucent ribbons flowing behind her without symbols, logos, markings, or text, neat composition, detailed eyes, cute and smart vibe, minimal background, polished illustration, no text
negative prompt: worst quality, bad eye, bad hand, extra limbs, manga, multiple views, monochrome, text, signature
dedup note: This article is distinct from ../git-reflog/, ../git-stash/, and ../git-rebase/. Those posts recover unreachable commits, temporarily store unfinished work, and rewrite commit history. This article focuses on choosing reset, restore, or revert from the working-tree/index/commit state, with safe undo semantics for local and shared history.
---&gt;
&lt;p&gt;





&lt;figure&gt;
    &lt;img class=&#34;my-0 rounded-md&#34; loading=&#34;lazy&#34; alt=&#34;featured&#34; src=&#34;./featured.png&#34; /&gt;

  
&lt;/figure&gt;
&lt;/p&gt;</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://dailypypy.org/learn/git-reset-restore-revert/featured.png" />
    </item>
    
    <item>
      <title>Git reflog 救援實戰：找回 reset、rebase 後消失的 Commit</title>
      <link>https://dailypypy.org/learn/git-reflog/</link>
      <pubDate>Fri, 21 Aug 2026 11:42:00 +0800</pubDate>
      
      <guid>https://dailypypy.org/learn/git-reflog/</guid>
      <description>&lt;!---
1440x768
prompt: masterpiece, best quality, highres, clean anime illustration, japanese anime style, soft shading, flat color design, 1girl, black hair, green eyes, white off-shoulder shirt, black short skirt, cowboy shot, slight side profile, one hand on chin thinking, relieved confident smile, looking at viewer, cream yellow background, subtle floating translucent timeline loops and small blank commit cards without symbols or text, neat composition, detailed eyes, cute and smart vibe, minimal background, polished illustration, no text
negative prompt: worst quality, bad eye, bad hand, extra limbs, manga, multiple views, monochrome, text, signature
dedup note: This article is distinct from ../git-rebase/, ../git-bisect/, and ../git-stash/. Those posts cover rewriting readable history, locating the commit that introduced a regression, and temporarily storing uncommitted changes. This article focuses only on local reference movement records, recovery anchors, unreachable commits, and safe restoration after reset, rebase, amend, or branch deletion.
---&gt;
&lt;p&gt;





&lt;figure&gt;
    &lt;img class=&#34;my-0 rounded-md&#34; loading=&#34;lazy&#34; alt=&#34;featured&#34; src=&#34;./featured.png&#34; /&gt;

  
&lt;/figure&gt;
&lt;/p&gt;</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://dailypypy.org/learn/git-reflog/featured.png" />
    </item>
    
  </channel>
</rss>
