Version control SVN and git simple combat summary
If you're not sure about version control in iOS development then you can take a look at this one (see again) It's not hard to use version control, but you might have a problem with it!
- Learn so many commands, feel that they know, and basically can knock out one or two, but it is not easy how to use the actual development of the company, or how I do, the following we come to the company after the first to do, and then often to do some things (command too many do not need to remember, It's just a few of the usual ones).
First of all, you must first know, in the celestial, SVN is currently the mainstream, but not not (here for specific reasons I will not say more)! Well, no more nonsense, just open the dry ... svn simple RoughTo the company, the first to get the corresponding server warehouse account and password first, the manager will give us to build a good project, and achieve the corresponding initialization we have to do is to hate simple, step by step can be the first step: into the corresponding folder, download our project to our computer checkout to achieve project file download, At this point in our local folder there will be a corresponding project file the next step is the real project development (here is no nonsense): After the development of a period of time, or to complete a small demand, the doubt after writing an important piece of code (recommended), will be submitted immediately. When the status is viewed above, if it appears? No, if it is not in the warehouse, this time we need to implement the following command to add or to add the corresponding file or the end is to submit our project or the above look relatively slow, then you can quickly according to the following command to learn how to use SVNgit simple roughWith the above, the project manager gave us a new project, and to implement the corresponding initialization first into the corresponding local folder, using the server warehouse account password to download the corresponding items to the local, this time will see our local folder has the server project source Then there's the real project development (that is, the hard-to-write code), and we're going to use Xcode to commit and update the commit directly--commit to the local and then commit to the remote repository. Or night can be submitted directly to the local and submitted to the remote repository when we want the latest code, we need to update the corresponding source (pull) Note in the server:
- The above steps basically achieve the corresponding requirements in the development, in the later development we just need to remember to submit our changes after each project, and often remember to update the server version to the local!
- The actual development of the use of these steps, some other attention to detail and related errors or conflicts in the following article, the author will be 1.1 points summary!
iOS development--development Combat & Version Control SVN and git simple combat summary
