Understanding Git and GitHub is crucial for any developer, providing effective version control and code management. Proficiency in these tools sets...
Some comments have been hidden by the post's author - find out more
For further actions, you may consider blocking this person and/or reporting abuse
Awesome Guide on Github Commands 🔥
Thanks for sharing this💖
Thanks for appreciation! ❤️
Wow interesting 👍🏾
prueba
Thanks for sharing!
that was great, but im stil confused on git resest part
could u just had added some visualize or example would be better
For example, your company wants to ship their product every Saturday night, but you, as a developer, mistakenly committed the changes before Saturday to the main
In that case, you need to remove the changes from the main branch. Removing the changes one by one may be complex. In that case, you just need to run the
git resetcommand to remove the last commit.Hope that makes sense.
really good article 👌
Awesome content!
Thanks for sharing! 💖
Would probably be a good idea to include a script that'd run on demand or per schedule that does pull for number of branches specified .
Yeah, that's a good idea, but it may not be efficient for the project, which took a long time to build. As it may be more prone to errors, like conflicts.
Thank you for sharing such powerful git commands... Very useful 😀👍🏻
Good content for those who are starting up.
Yeah, thanks 🙏
The issue I am experiencing with all the git tutorials up to now, including this one, is that they are based on git terminology which is poorly explained in first place, leaving room for contradictions making all the explanations useless. Let's take a look at the terms: repository, working directory and staging. In order to understand git I need a clear mental model of what git does and how. Explanations which change very quickly to the git vocabulary for describing what git does are not helpful. The general rule is that once you have got a concept to a level you start explaining you have lost the ability to see it from the perspective of knowing nothing about it and therefore unable to explain to someone who has trouble to grasp what it is all about, because up to now never in the actual need for coordination of a huge number of developers lacking therefore the awareness about what is needed, what for and why. In other words a well done explanation will first describe a well chosen and described case where with usual means it would be hard to impossible to accomplish something. This followed by the explanation of a solution would much more help to get the idea, the concept behind it all. In last step the vocabulary used as shortcut for lengthy descriptions can be presented making the meaning of git commands obvious.
Don't expect much of AI-created, artificially upvoted articles.
How to know which ones are they in first place before spending time on reading them?
Artificially upvoted articles are the ones that usually start with 5 reactions: One reaction each (heart, unicorn, mind-blowing, etc.). A few "authors" have access to more fake/bot accounts and their articles start with more reactions, but usually all individual reaction counts will be the same.
AI-created articles usually follow 2 or 3 very specific patterns, but most have a Conclusion section, use bulleted or numbered lists rather heavily and title hierarchies are always there. You'll get the hang of those rather quickly.
Oh, thanks... Very useful! ❤️
Very nice & detailed! Thank you
It's handy and day to day used git command.
Nicely explained.
Cheers!