[dgplug-users] Recovering commit after git reset --hard - A blog

Shashank Kumar abc at shanky.xyz
Sat Apr 7 12:47:05 PDT 2018


On Friday 06 April 2018 11:44 PM, Abhilash Raj wrote:

> On Mon, Mar 26, 2018, at 4:30 AM, Shashank Kumar wrote:
>> Hello folks,
>>
>> I hope you had a nice weekend. I for one struggled with one of my
>> projects which I had to present last week in college and made some
>> horrible choices with Git. I wrote my experience in a blog[0] and I hope
>> it would be informative for the folks facing the same problem. Reviews
>> and suggestions are always welcome. Thanks :)
> Great post!
>
> I'd suggest a `git cherry-pick <commit_hash>` as compared to `git reset --hard ...` again to recover the commit once you know the commit id just to make sure that you don't blow up anything else while trying to retrieve the lost commit.
That's way better. This way only adds lost changes as new changes. Thanks

Regards
Shashank | @realslimshanky <https://blog.shanky.xyz>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.dgplug.org/pipermail/users-dgplug.org/attachments/20180408/35f388cb/attachment.sig>


More information about the Users mailing list