PRE
发表于 2025-3-23 13:13:48
Diving into Project Management: Branchesange in our project. Our way of work was simple: choose an issue, make a commit that can resolve it, and push to GitHub. The issue was then resolved and closed. But this way of work is not very adapted in most real-world projects; the potential of screw-ups is too high.
floodgate
发表于 2025-3-23 14:16:29
Better Project Management: Pull Requests We also learned a lot about branches and how to use them. But there is one thing we didn’t get a chance to review: how to combine those two concepts. The answer is simple: Pull Requests and Code Reviews.
calumniate
发表于 2025-3-23 20:06:24
http://reply.papertrans.cn/19/1824/182342/182342_13.png
epinephrine
发表于 2025-3-23 23:17:58
http://reply.papertrans.cn/19/1824/182342/182342_14.png
袭击
发表于 2025-3-24 04:44:31
http://reply.papertrans.cn/19/1824/182342/182342_15.png
intimate
发表于 2025-3-24 08:36:08
Remote Gitfortable at making change and tracking them with Git. Writing meaningful commit messages is a little bit hard, but you will get better with each commit if you follow the last chapter’s advices. You should also be able to peek at a previous version and view the history logs; those are very important features needed for all further chapters.
Fluctuate
发表于 2025-3-24 14:37:00
http://reply.papertrans.cn/19/1824/182342/182342_17.png
Initial
发表于 2025-3-24 15:22:39
http://reply.papertrans.cn/19/1824/182342/182342_18.png
conspicuous
发表于 2025-3-24 21:19:02
http://reply.papertrans.cn/19/1824/182342/182342_19.png
SEED
发表于 2025-3-24 23:57:25
More About Conflictsn’t worry, this chapter will be much easier to digest. We are going to talk about how to get push your branch to remote after a merge conflict. Also, we are going to see some strategies to adopt to reduce the number of conflicts that might happen. Let’s go!