News for hackers. Stuff that matters.
Re:Moving and renaming files on GitHub by smoyer on Friday March 15, 2013 @04:53PM (#5382952)
Using the .. to traverse up the directory tree during a move operation is simply beautiful!
Re:Moving and renaming files on GitHub by modarts on Friday March 15, 2013 @05:14PM (#5383067)
I was just going to comment on that. Awesome example of a well targeted UX enhancement given the developer audience (this way of traversing a directory obviously wouldn't work for a product developed for terminal-averse users)
Re:Moving and renaming files on GitHub by tommoor on Friday March 15, 2013 @02:16PM (#5382078)
A neat feature, another step towards GitHub becoming the development IDE.
Re:Moving and renaming files on GitHub by msoad on Friday March 15, 2013 @05:04PM (#5383012)
Imagine if you get VI keyboard shortcuts for editor...
Re:Moving and renaming files on GitHub by bentaber on Friday March 15, 2013 @03:06PM (#5382336)
Solid use of animated gifs to get the point across.
Re:Moving and renaming files on GitHub by benackles on Friday March 15, 2013 @03:34PM (#5382497)
You rarely see an animated gif used for a practical purpose. It's usually followed by hysterical laughter. At least that's usually the intent.
Re:Moving and renaming files on GitHub by dfrey on Friday March 15, 2013 @03:46PM (#5382567)
How does this work? Is each rename a commit? That would really clutter up your history if for example you are trying to rename 10 .cc files to .cpp
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 :)
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/
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.
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.
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.
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.
Re:Moving and renaming files on GitHub by hawkw on Friday March 15, 2013 @02:01PM (#5381987)
Hooray! Now I can do all my work directly on GitHub.
Re:Moving and renaming files on GitHub by habosa on Friday March 15, 2013 @03:04PM (#5382320)
So now I can just do my work on Github. If Heroku could somehow auto pull and deploy I could approximate a reasonable workflow anywhere I have a browser. This is certainly awesome for hotfixes on the go when you're on some public computer.
Re:Moving and renaming files on GitHub by modarts on Friday March 15, 2013 @05:15PM (#5383079)
Check out Cloud 9 IDE. I found that I don't even need my high end MBPr to do my development work; and am getting by on my relatively under powered air.
Re:Moving and renaming files on GitHub by creativename on Friday March 15, 2013 @10:27PM (#5384116)
I second this - I've had great success using just Cloud9 for development and pushing to GitHub/Heroku
Re:Moving and renaming files on GitHub by bruth on Saturday March 16, 2013 @12:59AM (#5384521)
This is no good. I respect the UX of this feature, however I don't want new users to learn their git conventions in a browser, this way. I am not sure what GitHub's plan is for taking over the world.. but it would great for new users, if for each of their in-browser actions they provided help text that showed the corresponding CLI command. This reinforces their intent of these kinds of features.

EDIT: That is humorous.. I write the above only to see this: http://try.github.com/. It does not invalidate my argument, but it reinforces GitHub's motivation.

Re:Moving and renaming files on GitHub by recursive on Friday March 15, 2013 @07:03PM (#5383535)
Exciting. One step closer to never having to learn how to use git.
Re:Moving and renaming files on GitHub by TazeTSchnitzel on Friday March 15, 2013 @07:16PM (#5383588)
Which scares me. If the basic stuff can be done without git, but not the more advanced stuff, and beginners start to not learn git, they'll be hopeless when they need to do some sort of more advanced operation.
Re:Moving and renaming files on GitHub by zevyoura on Friday March 15, 2013 @09:37PM (#5383998)
Isn't that already the case in practice? Tons of devs just know git commit/push/pull and can't do much more without research.
Re:Moving and renaming files on GitHub by recursive on Friday March 15, 2013 @09:47PM (#5384030)
There are a lot of users that don't need the more advanced stuff.
Re:Moving and renaming files on GitHub by joejohnson on Friday March 15, 2013 @07:52PM (#5383713)
What does this do to the commit history for moved files?
Re:Moving and renaming files on GitHub by dunsudu on Friday March 15, 2013 @08:05PM (#5383755)
I guess it just checks the new file in and removes the old one. Git doesn't track file moves, except a posteriori.