Question, is it possible to do this code review on a standalone git server and not using third party such as github or bitbucket? If so, can anyone link me to the right resources? Thanks :)
Nice video, It would be helpful to teach people also how to set Develop branch as default. So each pull request will have to develop branch as default.
Good question :) I am often peerless but I follow the pull request process nonetheless. It's a useful habit to cultivate. I always review my own code before merging just to give it a second look.
Many aspects of the topic weren't covered. For example, what happens after finding bug and commenting? How the PR author fixes and resolves the issue? How the reviewer sees the fix and the comparison of the fixed file version to the original one? Etc. Very shallow tutorial.
Good video. Thank you for speaking so clearly without slang.
Mainly for those of us who do not usually hear English
You're welcome sir, thank you for watching and for the feedback.
Simple and great explanation. Thanks
Great video. Perfect level of detail and well explained.
Perfect video, clear and concise points! Keep it up
Very crisp and neat .. great explanation
Thanks a lot 😊
Thank you for teaching me. It's really helpful.
Love the way you explain things :), a great video
Very important things missed, like if someone asks you to make some changes then how do you do that and how does it reflect back in the pull request.
Great stuff, very concise and rich in content
Much appreciated!
Greatly explained
Awesome explanation, Thank you!
Glad you enjoyed it!
If I have a feature branch, is it a good practice to merge development down to the feature branch before the code review or any code compare?
Amazing video explained in great detail ❤️❤️❤️❤️❤️
Question, is it possible to do this code review on a standalone git server and not using third party such as github or bitbucket? If so, can anyone link me to the right resources?
Thanks :)
I think a very important thing missed in this video is how to get a commit down to your machine locally, otherwise, how can you review stuff?
Great Video
Nice video, It would be helpful to teach people also how to set Develop branch as default. So each pull request will have to develop branch as default.
Great video and some excellent points! What are your thoughts on pair programming?
not essential. peer reviews are the norm now
I often find it hard to navigate when multiple round of reviews. Can you show me how to navigate in that case
Great explanation. Thanks
really helpful.
great vid thank you
Perfect
Thanks!
What if you are peerless?
Good question :) I am often peerless but I follow the pull request process nonetheless. It's a useful habit to cultivate. I always review my own code before merging just to give it a second look.
Many aspects of the topic weren't covered. For example, what happens after finding bug and commenting? How the PR author fixes and resolves the issue? How the reviewer sees the fix and the comparison of the fixed file version to the original one? Etc. Very shallow tutorial.
Thanks for the honest peer review.
Excellent explanation! Thank you!