The fourth assistant training jobs - Proficiency GitHub and Git to use
Understand and use 1.Git command
Common Git commands to view official documents, official documents URL: https://git-scm.com/docs . While the interface is in English, but check out the official documents and more than blind to find information on the Internet come faster, or you can choose some of the more representative tutorials to learn, a lot to learn programming sites have Git Tutorial. Here are a few sites to learn git, personal advice to learn to see the official documents, although many features in the actual process is not used to, but the official interpretation of the document is generally more comprehensive in detail, and then go look up some online tutorials like blog It will be more deeply understood.
- https://www.nowcoder.com/courses/2 : Git & GitHub Start Basics
- https://progit.bootcss.com/#_pro_git : Pro Git Chinese version
- https://www.bootcss.com/p/git-guide/ : git - A Simple Guide
- https://www.w3cschool.cn/git/ : W3Schools tutorial Git
- https://www.runoob.com/git/git-tutorial.html : RUNOOB git tutorials
- https://www.liaoxuefeng.com/wiki/896043488029600 : Liao Xuefeng's git tutorials
- https://git-scm.com/docs : official document
Git commands used typically is in the form of a command line, of course, also comes with a git GUI graphical interface, but also can use TortoiseGit, uses a graphical interface, https://www.cnblogs.com/zlslch/p/ 7986039.html this blog a brief introduction to the difference between Git and TortoiseGit. Of course, individuals do not recommend beginners to start using TortoiseGit, git from the command line to start to learn, later re-use other tools naturally there would be much of a problem.
Git command is basically a file within a unified version of the warehouse management, before and after difference, change the details recorded version to help back the project development process.
2. The progress of the recording to a half unit of time, the submission of detection code, burndown
The development process, because in the past for Git and Github is little knowledge, so spend a lot of time learning these two things above, though still foggy now learned, can not understand and there are some local solutions, but I'll be in later years, as soon as possible to get rid of these problems themselves, can really master the use of these two tools. The burndown size issue because the set is too large, it set up a total of three issue, so it is not particularly good-looking show, and I do not know why, three close off the issue, the interface shows only two in the completion point .
As part of the code development, we completed the launch event first and second interface. This time because it takes a lot of time in learning Git and Github, so part of the development a little easier.
3. multiplayer collaborative development summary and reflection
The multiplayer collaborative development is really impressive, the first is the use of unskilled git and github, led to the development process of continuous re-created branch, re-cloning latest project, I personally think that this series development process is: first cloning project to a local warehouse, and then create your own branch, and push to the remote, and then complete their management in the local version, after the completion of a function point, it is pushed to the distal end of the individual branch, and then the contents of individual branches and development branch consolidation, if not automatically merge conflict, you need to manually resolve the conflict, the upcoming latest content development to the local branch of pulling the merger, pushed to the personal remote branch after conflicts resolved, and then the development branch merger, consolidation will continue if there is a conflict resolved. I do not know this argument right, is my personal understanding.
Perhaps my understanding there is a problem or what, there will always be some errors in the actual operation, in the development process, the biggest problem is not to resolve the conflict, the Internet search solution did not resolve the conflict arising out of, so we re-cloned over and over again, and then add their own content to the project, after re-cloning in general, subsequent merger can not go wrong, you can merge successfully.
Second, there is a problem that is really concrete realization merge function is not clear, see the online tutorials are written in simple, of course, a few URLs listed above, I have not seen all are all, so I do not know if I have detailed talked about the merge process, because I personally feel git version management, the most important thing is that step, introduce a simple command to merge is not enough, personally I think that the premise of conflict resolution is to know how to merge, Why would a conflict, these two points are more bothered me, because this job only two days, still no way to learn through git, so will the use of other times, strive to thoroughly understand these issues before the semester begins.
Then there's the issue size is set slightly large, so there is no good indication of the development process, the future will pay more attention to this aspect.
Finally I want to say is this collaborative development, though no substantive results did not get, but the good news is that the interface is more intimate look at Github, and not like before because of course do not understand, there is great resentment, so I do not like to use. Common git commands can also do not check the information, and really is practice makes perfect ah, too many times naturally back down. Discuss with other partners of the assistant makes me feel the joint efforts of a few people can indeed solve many problems and help each other. And they can work together very happy, we are all very hard worker, and everyone put a lot of effort into this job, because although the course of the semester for git and gituhub with simple awareness, but also simple to use, but are very, very shallow, so this takes a lot of time to carry out more in-depth study.