Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
Now you get to teach him about both ignoring files, and rewriting commit history!
-
And then you should restrict pushing to master and only authorize merge from dev.
-
gopher945yIn "master"? Then someone else made a mistake. Can't have the code of a person just learning git, just like that in master without a review.
-
@gopher Depends on the project and learning curve. Critical project, absolutely. But side project where there's one or two people working on it, and it's deliberately meant as a "let's keep Git as simple as possible" project - totally appropriate to forgo branches and commit to master.
-
@AlmondSauce if there’s enough folders for 200 .DS_Store files, I would say it’s time to add some basic restrictions for version control.
-
@gopher I wasn't aware that he was new to Git until the situation happened. Guess I should watch out in the future.
Working with someone who just learned Git.
Woke up this morning to 200 .DS_Store files on master.
-.-
rant