I am a Developer Advocate for Security in Mobile Apps and APIs at approov.io.
Another passion is the Elixir programming language that was designed to be concurrent, distributed and fault tolerant.
Location
Scotland
Education
Self teached Developer
Work
Developer Advocate for Mobile and API Security at approov.io
You can appreciate the joke as an experienced developer in git, that knows the implications of using it, but we need to be careful when trying to make jokes for the ones that don't get the context of it, specially when the article is targeting beginners.
I am a Developer Advocate for Security in Mobile Apps and APIs at approov.io.
Another passion is the Elixir programming language that was designed to be concurrent, distributed and fault tolerant.
Location
Scotland
Education
Self teached Developer
Work
Developer Advocate for Mobile and API Security at approov.io
Don't forget about:
:)Trololololol...
I appreciate the joke :)
You can appreciate the joke as an experienced developer in git, that knows the implications of using it, but we need to be careful when trying to make jokes for the ones that don't get the context of it, specially when the article is targeting beginners.
I thought it was pretty funny myself, but you also make a good point. Thank you for bringing it up!
I agree, hence my acknowledgement of the joke for what it is.
and
git pull origin master
git reset --hard
git stash
git stash pop
merging into master should be done via pull request imho
Cause you are on forked repo
This is a very bad advice, and should be never used, not even in solo projects, because you get into a bad habit that can have pretty nasty consequences in a professional environment, like Jenkin developers accidentally do "git push --force" to over 150 repos on github.
I don't have the link anymore, but I read a story once of a company that took months to recover from a
git push --force
to their master branch.To be on the safe side ALWAYS configure your Github, Gitlab or whatever you use to not accept push to
master
.