cool hit counter Detailed Steps for Local Configuration of Git Server_Intefrankly

Detailed Steps for Local Configuration of Git Server


In the development process we can't be independent, usually it's a teamwork development, in this case we end up with a lot of problems when merging the code, after all, everyone has their own way of writing, in order to merge the code when it's easy to merge, so we use Git.

When I first started using Git, I found a lot of information on the Internet, and the talk was really exaggerated. Let me give you the details on how to configure Git.

I. Installing Git

Git is available for download at https://git-scm.com/downloads

Installation steps: Link: https://pan.baidu.com/s/1U2fgSvgvb8dDeEioY0Bsxw Password: auy7

II. Local configuration

View self contained configuration information

Configure username

Configure email

Check if the configuration is successful

Go to the local Git repository and initialize git

Show hidden folders

Go to the file to see Note: The .git folder should never be modified

All files have to be placed under E:GitdbStudyGit Git will only organize the files

The file has only been added to the workspace but not to the staging area

Adding files to the staging area

Check the status of the git server again (successfully added to the staging area)

Submitting files to the local server

Checking the git staging area again, there are no more files

Modification of documents

Check the git staging area again. The file is colored red to indicate that Git has detected a change to the file.

Commit the modified file again and check the git staging area for the file

If the file to be submitted is long, do not use the above command

I'm sure those of you who use C or Linux are no stranger to this interface

I created a new .tst text before, now I deleted it and created a new .txt text

Contrast the difference between the staging area and the work area

It makes no difference if you check it after you submit it

See the difference between staging areas and local repositories

Checking in after submission reveals the same

There are two cases here, one when there are files in the staging area and the other when there are no files in the staging area.

(1) When there are no files in the staging area, git diff compares the files in the workspace with the files in the last commit to the repository.

(2) When there are files in the staging area, git diff compares the files in the current workspace with the files in the staging area.

And git diff HEAD -- file, which compares the differences between the files in the workspace and the files in the repository. HEAD points to the current version in the repository, and file refers to the file in the current workspace.

There are two types of revocation operations

(1) Modify the file undo operation in the workspace !!! Change to.

(2) You want to withdraw after submitting to the staging area

When data is committed from the staging repository to the repository only version rollback can be performed Here are the detailed steps

Check the committed version first, then do a fallback

Now back up to the version just backed up

doc file download at.

https://download.csdn.net/download/internetprogrammers/10504410

Recruiting programmers for seafarers

Make programming a pleasure

Personal WeChat


Recommended>>
1、DynamicGoogle Releases Machine Learning Rules on Best Practices for Machine Learning Engineering below
2、Express Flying taxi company to trial in Paris next year Nature paper using machine learning to predict autism
3、Protocol
4、10 mustknow tools for programmers
5、Introduction to Regular Expressions

    已推荐到看一看 和朋友分享想法
    最多200字,当前共 发送

    已发送

    朋友将在看一看看到

    确定
    分享你的想法...
    取消

    分享想法到看一看

    确定
    最多200字,当前共

    发送中

    网络异常,请稍后重试

    微信扫一扫
    关注该公众号