News for hackers. Stuff that matters.

A comment on Moving and renaming files on GitHub. Parent comment

Re:Moving and renaming files on GitHub by cobychapple on Friday March 15, 2013 @04:26PM (#5382804)
Yes. Each rename (and any updates to content that happen at the same time) is just a new commit on the branch you do the edit on. It should produce identical history to doing the same operation via the command-line :)
[ Parent | on HN ]
Re:Moving and renaming files on GitHub by masklinn on Friday March 15, 2013 @05:14PM (#5383073)
On the command line, I can do multiple renames in a single commit/
[ Parent | on HN ]
Re:Moving and renaming files on GitHub by mtodd on Friday March 15, 2013 @06:34PM (#5383402)
If you want to do multiple renames in one commit then the command line is likely the best way.
[ Parent | on HN ]
Re:Moving and renaming files on GitHub by buttscicles on Friday March 15, 2013 @08:02PM (#5383747)
Alternatively use this feature and squash them later when you have access to a terminal.
[ Parent | on HN ]
Re:Moving and renaming files on GitHub by mineo on Saturday March 16, 2013 @08:53AM (#5385279)
In that case you'd need to either force the next push because squashing rewrites history or use a separate branch to do the renames in the first place.
[ Parent | on HN ]
Re:Moving and renaming files on GitHub by dbaupp on Friday March 15, 2013 @05:06PM (#5383023)
I think dfrey means that you have 10 commits, rather than just one.
[ Parent | on HN ]