Following Git(Hub) History
Does anyone have any strategies for following git histories past code reorganizations (see steps #2 and #5 below)? My typical experience is: 1. Do blame or history on a file 2. Follow it back to the inevitable "convert to tonel" 3. Go to that commit's parent 4. View repo files at that point 5. Follow back to "rename code subfolder" 6. Repeat steps 3 - 5 as necessary until I find the version I need or "initial commit porting from StHub!" ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
El 6 ago 2019, a las 0:48, Sean P. DeNigris <sean@clipperadams.com> escribió:
Does anyone have any strategies for following git histories past code reorganizations (see steps #2 and #5 below)?
My typical experience is: 1. Do blame or history on a file 2. Follow it back to the inevitable "convert to tonel" 3. Go to that commit's parent 4. View repo files at that point 5. Follow back to "rename code subfolder" 6. Repeat steps 3 - 5 as necessary until I find the version I need or "initial commit porting from StHub!â
Have you tried a $git log âfollow ? The follow option will take into account file renames and moves, simplifying at least steps 3-6.
----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
Guillermo Polito wrote
$git log âfollow
Didn't know about that one. Thanks! I'll try and report back... ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
participants (2)
-
Guillermo Polito -
Sean P. DeNigris