Комментарии:
Thanks.
ОтветитьI found gold
Ответитьexcellent video!
ОтветитьGood explanation
Ответитьone of the best shortest practical video explanation on github. I have seen many videos they are only theory and even some of them are not showing practical but u r video is just like begginer of the github can even understand it tq very much
ОтветитьThank you so much for this... I was confused watching a lot of other tutorials but this cleared my doubts
ОтветитьThank you.
ОтветитьGreattt Video was very helpful
ОтветитьThank you so much. You’ve answered all my questions on collaborations.
ОтветитьThanks a lot , u have saved a lot of hours for me
ОтветитьQuestion: what is the point of delete the older ticket branch if it doesnt remove the branch on github?
Ответитьmuch appreciated brother
ОтветитьGreat video! Super clear and to the point! A lot of other tutorials dont cover the team working workflow but this is gold! What about using more branches like release and hotfix? Are there good examples how to use those? Greetings from germany 🙂
Ответитьbut shouldnt the pull origin master be before pushing the feature branch?
ОтветитьThanks man
ОтветитьGreat simple video, helped me a lot, thank you!
Ответитьwhy "pull origin master" when you are about to delete the branch?
ОтветитьThat's an awesome practical tutorial.. Thanks
Ответитьshoutout to all the oldschool coders that did not abandon SVN for git
ОтветитьThis was a great video for me to document the git process for my team, thanks!
ОтветитьJust what I needed, legend
ОтветитьExtremely helpful! Thanks!
ОтветитьWell explained! I was struggling trying to understand how to do certain functionality prior to watching this and now my questions have been answered. Thank you!
ОтветитьDoes pushing local branch to github automatically creates pull request( merging the branch to master branch) ?
ОтветитьAwesome Explanation. Very Straight forward. Can you clarify my doubt. I am new to git. In your video when you pushed new branch to remote. Branch created in Origin with All Files, in that Branch we see all files instead of just Committed files. You committed only one file right .. But we see 2 files in that newly created branch.
In My Project I have 100's of files For every small change if i push that branch, All files will be pushed.
Can i Create New Branch with Only Committed files ?
Thank You
Please, can anyone help
When you clone repository - did you do it on the companies repository or we should fork, and clone from the copy of our account?
Thanks a lot!
ОтветитьThank you very much!
ОтветитьAwesome video, I had so much trouble resolving merge conflicts before. Is there a certain extension needed in VScode to get those accept changes options?
ОтветитьHELP
ОтветитьThanks for this video, I learn a lot from this!
ОтветитьThank you so much. Very informative video.
ОтветитьAmazing...
ОтветитьThanks a lot. Very useful and straightforward 🙌🙌
ОтветитьI like how you get to the point with this video. Great examples showing a successful merge and resolving a conflict. When you are on a tix-5 branch, does that the tix-5 branch show up on your local file directory? I see you can confirm which branch you are on in the terminal, but I am curious if you can visualize it when you're working on local? thank you.
ОтветитьThank you so much for the video! This has helped me tremendoulsy at my first job!
Also the book Code Complete that you suggested in the video description is a winner! A big big big reason why i was able to get past some of my tech interviews while applying to jobs. If you haven't read code complete i highly suggest checking it out. Link in bio!!
hey, how'd you get your terminal to look like that?
ОтветитьWonderfull
Ответитьwhat is the -A parameter used for? Looks like an "all" but git add already does that so it's why i'm asking.
ОтветитьThis is the best! Can you tell us more what happens if you find sth wrong after pushing to origin
ОтветитьSo helpful for us noobs man, thank you for making this
Ответитьhelped much! Thank you!!
ОтветитьI was curious about the private repo, how I will add contributors, and how to put limited access, such as branches, so they could not push changes to the repo as origin main or master.?? Thank you very much!!!
ОтветитьLoving it , Thanks man!
ОтветитьConstantly pull from master ? Or branch we create day by day?
ОтветитьHere's a scenario:
Time 1: A created a feature branch based on master.
Time 2: A worked on 1 commit on the feature branch.
Time 3: There is a new commit (maybe a merge) in the master branch.
Time 4: The next day, A wants to continue to work on the feature branch.
Question:
Should he do a git pull in the morning before doing his work?
Also, after the pull, how should he incorporate the changes in master into his feature branch? Or should he?
Lastly, if the changes in master totally removed some main functions where his feature branch is based on, what should he do?
Thank you!!
thanks, exactly what i was searching for ! your tutorial + chatgpt for more in depth explanations allowed me to understand everything. A pain point for me was that i didn't understand the merge process when there is a conflict. In my mind, github wouldn't "assume" that you have solved all the changes
ОтветитьThank you for the video
Ответить