169 likes
·
4.5K reads
18 comments
Well curated and nicely explained Tejansh. I don't use GitHub much, but liked reading what your article is saying. In simple words, you explained a very complex content 👼
Really liked reading it⚡
Would like to wish you a very all the best for everything in life🎎 May you bring more and more Contents that explain huge concepts in simple lines.
Keep going 😊
Thank you Manish⚡Nayak! That is incredibly kind of you. I wish you all the best for everything too 🙂
Thanks for this amazing write-up! Thanks, brother 👏
Thank you Savio Martin! 🙂
Can you told me about an app which you use in the main picture? Is just an image or this is the external app?
Hi Michał Wójcik, sure, that's an image by Yancy Min I found on unsplash. Here's the link to the original image - unsplash.com/photos/842ofHC6MaI 🙂
Might be gitkraken.com
Tejansh Rana - thanks ;-)
Zachary Dixon - I using gitkraken but this isn't 1:1 like on the image. On the image on the left sidebar, we have folder/file tree + main window git branches. I was hoping this is a good addon for ide ;D
I see what you mean Michał Wójcik. Yes, you get a very similar looking feature in the IDEs from JetBrains like IntelliJ where you can visualise the git flow. 🙂
I really liked the idea of opening the multiple PR against the own branch for huge changes. Having gone through a migration I feel that this would have helped the team members review the PR a lot faster without loosing interest in reviewing/testing it.
Thank you Jay. This has helped us a lot and we actively follow it when working on chunkier tasks like building the boilerplate code for a new project/microservice 🙂
Great article, Tejansh Rana! 👏
I enjoyed it, especially these points:
- Break it down to smaller PRs against your own branch and get that reviewed.
- Add all the relevant information that you can to the PR.
- A suitable title for your PR can also give clarity to the reviewer before they even read the description.
Thank you Catalin Pit! 🙂
Great article
Thank you Suraj Shende! 🙂
It is much better to use gitflow. datasift.github.io/gitflow/IntroducingGitF…
Sorry, what is it better for?
Nandy Legorreta if you mean for git branch management, here is what the author of Gitflow has to say about it - nvie.com/posts/a-successful-git-branching-…
TL;DR: It is a 10 year old model which is no longer recommended due to various constraints and since the workflow in Github has advanced significantly since. 🙂