(30:20) Comparing branches Just a short note: if you use _three_ dots instead of two you'll see _all_ the differences in commits between branches, so not only commits that are in the second branch compared to the first but vice versa as well. Excellent intro to branches, very concise.
As a newbie to GitHub this is without a doubt the best, clearest and most informative demo of branching I've seen. I've learnt a lot from this - thanks for sharing
I've learnt so much in this channel, I think I should tell my mother to bring you some goat milk :)) (we're nomads, it's costumery to give goats and goat products as gifts.)
@@shauryakapoor2122 well I grew up in a city, so we do have net. But my parents where nomads for the first part of their life. Then my father went to school and became a health care worker, and was hired by the government, so technically we're not nomads any more, but my mother still does give people goat milk as a gift :))
Because you are a descendent of a nomad family, you are a nomad (in culture) and this might not mean technically you are nomad. That is also me, although I lived my whole life in a city, and I had ps1, ps2, ps3, ps4, pc, I am a software development employee, and my parents have degrees, but my grand grandparents were nomad, because of the high poverty at that time, so they have traveled a lot, and suffered, and we took their culture and manners.
Please add Polish subtitles in the future, I am learning English along with programming and I admit that sometimes I do not understand what is being said. I really don't know a more valuable channel. Congratulations for your work!
Great tutorial! Although I would've chosen different names for branches as it makes it confusing to follow up. If the command is called "branch" then I wouldn't name my branch "my-branch" as there are too many occurrences of "branch". Or "uploader" as the name of a branch to be uploaded causes you to say things like "I'll upload my uploader", which can be confusing for beginners. Other than that, great sound quality, great flow and great content.
'git push --delete origin feature/branch' is easier to remember, because the delete flag is of the push operation and then the location and object are given :)
Hi, I did some changes on a file locally (It's the only existing file...) but I didn't add it to the git project. Instead I created a new branch and made it active. Then I added the new modifications and commited them. I didn't push it yet to the remote repo. How can I access the unchanged (.pdf) file locally, say with adobe pdf-reader?
In the pdf file "working with branches in git" it says under publishing branches, that you can't create a branch remotely but instead you have to push the local one. So I did. But in github I couldn't see the new branch until I entered a name (the same one as locally) in a window called: "Find or create a branch". After that I could see the new branch also remotely. What is now correct?
If i am in master branch and create a new branch the way it is described here, all the changes that i make on the new branch get automatically pushed to my master branch (and if i want to merge, git says my branch is already up to date). Can anybody explain?
For some reason I filled out the form 3 times over the last 3 months and can't seem to get the cheatsheet. Is there a way to just download it instead of having the download emailed?
The course is great but never get to manage to get a cheatsheet. Too many clicks and always found myself in the loop. Never get the download link only email with Tower picture and confirm subscription. After confirmation it opens Tweet for the T-shirt and ....well the web is full of cheatsceats anyway so I stoped researching why is this happening. thanks tobias for explaining branches
This video is a bit misleading. It only talks about the practical part of git branches. It didn't talk about what a git branch is and whether it's needed, when to use one, when not to use branches and the title didn't state whether it's for beginners or professionals. But I won't dislike it because it did at least explain how to create branches and work with them. You should change the video title to "How to work with git branches". I was looking for a more in-depth tutorial
While I appreciate your dedication, however you have contradicted yourself. You said you will be doing everything from the cli but you constantly referred to your git UI instead of using the cli, NOT COOL
Worst tutorial ever. Why ? It's a brilliant exhaustive documentation of how git does things. Period. But what, in my daily dev ops, shoud require to create a branch, to merge it or not, to push it or not, ... Nothing here to help you to link every day dev ops tasks to git commands listed here. Useless.
