#Git discard local changes software#
These branches provide an untouched history of your repository, documenting your features and software releases. Public branches like master are ones that your team regularly merges work into via pull requests and that nobody commits to directly. With git tutorials, it’s often difficult to accurately simulate the real world, where you most likely will not be committing directly to master, and where you’ll be working with other developers. env to git, good eye! We’ll delete that later.) A Note on Modifying Public Branchesįor me to come up with reproducible code samples for this tutorial-and for you to be able to easily run them on your end-we’ll be executing most git commands directly on master itself. (Also, if you’re concerned that we added an. Obviously, your commit hashes will differ from mine.įeel free to follow along and run these commands-the best way to learn git is to use git! * 0beebfb - Add package.json (5 seconds ago) On my end, that gives me this history: * 4753e23 - (HEAD -> master) Add. & git commit -m "Add package.json" & \ echo FOO =bar >. Before we get to the examples, let’s create a simple git repo with a few commits: git init & \ echo > package.json & git add.
0 kommentar(er)
