git 详细教程，从头开始，看简单英文比中文好懂

最新推荐文章于 2026-05-21 07:34:36 发布
原创 最新推荐文章于 2026-05-21 07:34:36 发布 · 1.6w 阅读 · 4 ·
本内容遵循CC 4.0 BY-SA版权协议
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文是一份Git教程，涵盖了从设置用户名和邮箱开始的基础知识，包括创建本地仓库、克隆远程仓库、新增文件并推送、获取远程仓库更新。对于进阶用户，介绍了分支管理、打标签、修改远程分支、重命名分支以及对比差异等高级操作。

Get started

Setting up your username and email

  • GIT records your name and email address with every commit you make, so the first step is to tell GIT what these are so you can get credit for your work
GIT command
$ git config --global user.name 'Your Bitbucket username'
$ git config --global user.email you@somedomain.com
Sample Usage
$ git config --global user.name 'ravidte'
$ git config --global user.email 'ravid.te@owmessaging.com'


Beginner

 

PLEASE NOTE, Section I and II below, are not to be followed in order, they are 2 separate Actions (one to create a new local git repo to push to remote GIT, and the other to obtain "clone" an existing repo from GIT).

Please use one or the other for your purposes.

 

      NOTE:  Using Project DEVOPS for Sample Usage Examples


I. Version controlling your existing project
  • "git init" can be used to create a new GIT repository by converting an existing unversioned project to a GIT repository or initializing a new empty repository.
GIT command
$ cd ~ /workspace/project
$ git init
$ git remote add origin git@bitbucket.org:openwave/{reponame}.git
$ git pull origin master
$ git add <files>
$ git commit -m "JIRAKEY comment"
$ git push origin master
Sample Usage
$ cd ~/Work/AUTOMATION/
$ git init
Initialized empty Git repository in /Users/rte/Work/AUTOMATION/.git/
$ git remote add origin git @bitbucket .org:ravidte/testmigration.git
$ git pull origin master
remote: Counting objects: 5 , done.
remote: Compressing objects: 100 % ( 2 / 2 ), done.
remote: Total 5 (delta 0 ), reused 0 (delta 0 )
Unpacking objects: 100 % ( 5 / 5 ), done.
From bitbucket.org:ravidte/testmigration
  * branch            master     -> FETCH_HEAD
$ git add .
$ git status
# On branch master
# Changes to be committed:
#   (use "git reset HEAD <file>..." to unstage)
#
#    new file:   testfile1.java
#    new file:   testfile2.java
#    new file:   testfile3.java
#
$ git commit -m "DEVOPS-243 adding new project to test migration"
[master 64a0261] DEVOPS- 243 adding new project to test migration
  3 files changed, 3 insertions(+)
  create mode 100644 testfile1.java
  create mode 100644 testfile2.java
  create mode 100644 testfile3.java
$ git push origin master
Counting objects: 6 , done.
Delta compression using up to 4 threads.
Compressing objects: 100 % ( 2 / 2 ), done.
Writing objects: 100 % ( 5 / 5 ), 389 bytes | 0 bytes/s, done.
Total 5 (delta 0 ), reused 0 (delta 0 )
To git @bitbucket .org:ravidte/testmigration.git
    7448278 ..64a0261  master -> master

 



II. Cloning the codebase from remote GIT Bitbucket repository

  • "git clone" will copy the entire history of a project so you have it locally and it will give you a working directory of the main branch of that project so you can look at the code or start editing it. If you change into the new directory, you can see the .git subdirectory - that is where all the project data is.
GIT command
$ git clone https: //yourbitbucketusername @bitbucket.org /openwave/repo .git
Sample Usage
$ git clone https: //ravidte@bitbucket.org/openwave/devops.git
Cloning into 'devops' ...
Password for 'https://ravidte@bitbucket.org' :
remote: Counting objects: 11 , done.
remote: Compressing objects: 100 % ( 6 / 6 ), done.
remote: Total 11 (delta 0 ), reused 0 (delta 0 )
Unpacking objects: 100 % ( 11 / 11 ), done.
Checking connectivity... done





III.  Create a new file and push it to the remote Bitbucket Git repository

 

  • use "git add" to start tracking new files and also to stage changes to already tracked files
  • use "git commit" to record the items you have staged (using git add),the -m option provides the commit message in which a JIRAKEY is required as a prefix to the commit message
  • use "git push" to move/push your changes to the remote repository
GIT command
$ git add
$ git commit -m "JIRAKEY-123 short but descriptive commit message"
$ git push

NOTE: Wildcards can be used:

To add all files: git add *

To add all txt files:  git add *.txt

Sample Usage
$ cat > test.out
this is some text
$ git status
# On branch master
# Untracked files:
#   (use "git add <file>..." to include in what will be committed)
#
#    test.out
nothing added to commit but untracked files present (use "git add" to track)
$ git add test.out
$ git status
# On branch master
# Changes to be committed:
#   (use "git reset HEAD <file>..." to unstage)
#
#    new file:   test.out
#
$ git commit -m "DEVOPS-243 added test.out file"
[master 8b67d01] DEVOPS- 243 added test.out file
  1 file changed, 1 insertion(+)
  create mode 100644 test.out
$ git status
# On branch master
# Your branch is ahead of 'origin/master' by 1 commit.
#   (use "git push" to publish your local commits)
#
$ git push
Password for 'https://ravidte@bitbucket.org' :
Counting objects: 4 , done.
Delta compression using up to 4 threads.
Compressing objects: 100 % ( 2 / 2 ), done.
Writing objects: 100 % ( 3 / 3 ), 329 bytes | 0 bytes/s, done.
Total 3 (delta 0 ), reused 0 (delta 0 )
To https: //ravidte@bitbucket.org/openwave/devops.git
    fa42bbc..8b67d01  master -> master
ravids-imac:devops vid401t$ git status
# On branch master
nothing to commit, working directory clean

NOTE: "git status" used above is to showcase the status changes for each command, it is completely optional to use, but recommended to verify execution

 

 

IV.  Deleting a file from the remote Bitbucket Git repository

 

 

GIT command
$ git rm filetoberemoved
Sample Usage
$ git rm test.out
rm 'test.out'
$ git commit -m "DEVOPS-243 deleting test.out"
[master 7448278 ] DEVOPS- 243 deleting test.out
  1 file changed, 1 deletion(-)
  delete mode 100644 test.out
$ git push
Password for 'https://RavidTe@bitbucket.org' :
Counting objects: 3 , done.
Writing objects: 100 % ( 2 / 2 ), 210 bytes | 0 bytes/s, done.
Total 2 (delta 0 ), reused 0 (delta 0 )
To https: //RavidTe@bitbucket.org/RavidTe/testmigration.git
    7e574ff.. 7448278  master -> master
$ git status
# On branch master
nothing to commit, working directory clean

 

 

V.  Get updates to your local workspace from a remote repository

 

You can use two methods

  • git fetch & git merge
  • git pull

 

git fetch will update your local remote tracking branches but not your local workspace

git pull will update your local remote tracking branches as well as your local workspace with changes

 

GIT command
$ git fetch
$ git whatchanged ...origin
$ git merge
Sample Usage
$ git fetch
remote: Counting objects: 4 , done.
remote: Compressing objects: 100 % ( 2 / 2 ), done.
remote: Total 3 (delta 0 ), reused 0 (delta 0 )
Unpacking objects: 100 % ( 3 / 3 ), done.
From https: //bitbucket.org/openwave/devops
    bef508d..b7f730c  master     -> origin/master
$ git status
# On branch master
# Your branch is behind 'origin/master' by 1 commit, and can be fast-forwarded.
#   (use "git pull" to update your local branch)
#
nothing to commit, working directory clean
$ git whatchanged ...origin
commit b7f730c4ecedd250975cec3ec7b43c01c157fe0a
Author: ravidte-owmessaging <ravid.te @owmessaging .com>
Date:   Thu Feb 27 13 : 37 : 06 2014 - 0500
 
     Added new file
 
: 000000 100644 0000000 ... fa49b07... A  newfile.txt
$ git merge origin/master
Merge made by the 'recursive' strategy.
   newfile.txt | 1 +
   1 file changed, 1 insertion(+)
   create mode 100644 newfile.txt

Intermediate

      NOTE:  Using Project DEVOPS for Sample Usage Examples

I. Branching and merging

  • "git branch" gives you a list of all the branches (use -v for more detail, eg. git branch -v)
  • "git branch branchname" is used to create a new branch
  • "git checkout branchname" let's you switch to the branch
  • "git merge branchname" this let's you merge your current active branch with the other branch
  • "git branch -d branchname" this deletes the mentioned branchname

 

Scenario:  An urgent fix is needed to fix DEVOPS-242

GIT command
$  git status
$ git branch <somebranchname>
$ git checkout <somebranchname>
$ git add <file>
$ git commit -m  "JIRAKEY comment"
$ git checkout <master>
$ git merge <somebranchname>
$ git branch -d <somebranchname>
Sample Usage 
$ cd ~/workspace/project
$ git status
# On branch master
nothing to commit, working directory clean
$ git branch -v
* master f59726b DEVOPS-241 added the missing footer
$ git branch DEVOPS-242
$ git branch -v
  DEVOPS-242 f59726b DEVOPS-241 added the missing footer
* master     f59726b DEVOPS-241 added the missing footer
$ git checkout DEVOPS-242
Switched to branch 'DEVOPS-242'
$ vim index.html
$ git add index.html
$ git commit -m "DEVOPS-242 fixed closing tag of footer div"
[DEVOPS-242 451f2d4] DEVOPS-242 fixed closing tag of footer div
 1 file changed, 1 insertion(+), 1 deletion(-)
$ git status
# On branch DEVOPS-242
nothing to commit, working directory clean
$ git checkout master
Switched to branch 'master'
$ git merge DEVOPS-242
Updating f59726b..451f2d4
Fast-forward
 index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
$ git branch -v
  DEVOPS-242 451f2d4 DEVOPS-242 fixed closing tag of footer div
* master     451f2d4 DEVOPS-242 fixed closing tag of footer div
$ git branch -d DEVOPS-242
Deleted branch DEVOPS-242 (was 451f2d4).
$ git branch -v
* master 451f2d4 DEVOPS-242 fixed closing tag of footer div

 



II. Creating and using tags

  • "git tag"  let's you tag specific points in history as important
  • "git checkout <tagname>"
  • "git describe"
GIT command 
$ git status
$ git tag <tagname>
$ git add <file>
$ git commit -m "JIRAKEY comment"
$ git describe --tags
$ git push origin <tagname>

NOTE:  if you want to push all your tags, you can use --tags, eg.  git push origin --tags

NOTE: you can also create branches from tags, eg. git checkout -b <branchname> tagname 

Sample Usage 
cd ~/workspace/project/
$ git status
# On branch master
nothing to commit, working directory clean
$ git tag
$ git tag v0
$ git tag
v0
$ vim index.html
$ git add index.html
$ git commit -m "Version 1.0"
[master 830f4e6] Version 1.0
 1 file changed, 2 insertions(+), 1 deletion(-)
$ git tag v1
$ git tag
v0
v1
$ git describe --tags
v1
$ git checkout v0
Note: checking out 'v0'.
 
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
 
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
 
  git checkout -b new_branch_name
 
HEAD is now at 451f2d4... DEVOPS-242 fixed closing tag of footer div
$ git describe --tags
v0

 

 

 

III. Modifying remote branches

  • "git checkout -b <new local branch> <remote branch> , this will create a copy of the remote branch to your local workspace as the "new local branch"

 

GIT command 
$ git status
$ git branch -a
$ git checkout -b <local branch> <remote branch>
$ git commit -m "JIRAKEY comment"
$ git push
Sample Usage 
cd ~/workspace/project/
git status
# On branch master
nothing to commit, working directory clean
$ git branch -a
* master
  remotes/origin/HEAD -> origin/master
  remotes/origin/cox
  remotes/origin/master
  remotes/origin/release_1-5-1
  remotes/origin/sbm
  remotes/origin/vm
$ git checkout -b release_1-5-1 origin/release_1-5-1
Branch release_1-5-1 set up to track remote branch release_1-5-1 from origin.
Switched to a new branch 'release_1-5-1'
$ vim ravid.test
$ git add ravid.test 
$ git commit -m "JIRA-123 made changes to ravid.test"
[release_1-5-1 bcb194f] made changes to ravid.test
 1 file changed, 1 insertion(+), 1 deletion(-)
$ git push

Counting objects: 5, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (2/2), done.
Writing objects: 100% (3/3), 286 bytes | 0 bytes/s, done.
Total 3 (delta 1), reused 0 (delta 0)
To https://ravidte-owmessaging@bitbucket.org/ravidte-owmessaging/ravid-testfork.git
   a48d7c5..bcb194f  release_1-5-1 -> release_1-5-1

 

 

 

IV. Renaming remote branches

  • "git branch -m <old branch name> <new branch name>  , this will change the local branch name
  • "git remove -v" , this checks which remotes you have (assuming origin for these steps)
  • "git push origin :<remote branch to delete>"  , this will delete the remote branch
  • "git push origin <new branch name>"  , this will push the new branch name to the remote

 

GIT command
$ git banch -m <old branch name> <new branch name>
$ git push origin :<remote branch to delete>
$ git push origin <new branch name>
Sample Usage
git status
# On branch master
nothing to commit, working directory clean
$ git branch -m features feature- 123
$ git remote -v
origin    https: //ravidte-owmessaging@bitbucket.org/ravidte-owmessaging/devops-ci.git (fetch)
origin    https: //ravidte-owmessaging@bitbucket.org/ravidte-owmessaging/devops-ci.git (push)
$ git push origin :features
To https: //ravidte-owmessaging@bitbucket.org/ravidte-owmessaging/devops-ci.git
  - [deleted]         features
$ git push origin feature- 123
Counting objects: 4 , done.
Delta compression using up to 4 threads.
Compressing objects: 100 % ( 2 / 2 ), done.
Writing objects: 100 % ( 3 / 3 ), 315 bytes | 0 bytes/s, done.
Total 3 (delta 0 ), reused 0 (delta 0 )
To https: //ravidte-owmessaging@bitbucket.org/ravidte-owmessaging/devops-ci.git
  * [ new branch]      feature- 123 -> feature- 123

 



V.  Diff changes

 

  • use "git diff" to see what is still unstaged
  • use "git diff -staged" to see what you have staged so far
  • use "git reflog" provides a list of hashes which represent where you have been
  • use "git diff <#commithash> <#commithash>" to compare differences between commit's
GIT command 
$ git diff
$ git add <file>
$ git diff --staged
$ git commit -m "JIRAKEY comment"
$ git reflog
$ git diff <#commithash> <#commithash>
Sample Usage 
cd ~/workspace/project/
$ git diff
$ vim index.html 
$ git diff
diff --git a/index.html b/index.html
index 957cbfb..5fced4a 100644
--- a/index.html
+++ b/index.html
@@ -14,6 +14,7 @@
 
        This is another line I need to add
 
+        This is a git diff test
 
        <div id=footer> Fix for DEVOPS-242 this is the footer </div>
 </body>
$ git add index.html 
$ git diff --staged
diff --git a/index.html b/index.html
index 957cbfb..5fced4a 100644
--- a/index.html
+++ b/index.html
@@ -14,6 +14,7 @@
 
        This is another line I need to add
 
+        This is a git diff test
 
        <div id=footer> Fix for DEVOPS-242 this is the footer </div>
 </body>
$ git commit -m "DEVOPS-242 this was a diff test"
[detached HEAD c1e21e8] DEVOPS-242 this was a diff test
 1 file changed, 1 insertion(+)
$ git reflog
c1e21e8 HEAD@{0}: commit: DEVOPS-242 this was a diff test
451f2d4 HEAD@{1}: checkout: moving from master to v0
830f4e6 HEAD@{2}: commit: Version 1.0
451f2d4 HEAD@{3}: merge DEVOPS-242: Fast-forward
f59726b HEAD@{4}: checkout: moving from DEVOPS-242 to master
451f2d4 HEAD@{5}: commit: DEVOPS-242 fixed closing tag of footer div
f59726b HEAD@{6}: checkout: moving from master to DEVOPS-242
f59726b HEAD@{7}: commit: DEVOPS-241 added the missing footer
8c31443 HEAD@{8}: commit: DEVOPS-242Added some code in the body
19205aa HEAD@{9}: merge DEVOPS-243: Fast-forward
fa5c22e HEAD@{10}: checkout: moving from DEVOPS-243 to master
19205aa HEAD@{11}: commit: test
fa5c22e HEAD@{12}: checkout: moving from master to DEVOPS-243
fa5c22e HEAD@{13}: commit: Added a test alert to index.html
222e5cc HEAD@{14}: commit (initial): Adding new file index.html
$ git diff 451f2d4 c1e21e8 
diff --git a/index.html b/index.html
index 957cbfb..5fced4a 100644
--- a/index.html
+++ b/index.html
@@ -14,6 +14,7 @@
 
        This is another line I need to add
 
+        This is a git diff test
 
        <div id=footer> Fix for DEVOPS-242 this is the footer </div>
 </body>

git merge <branch_name> 合併另一個 branch，若沒有 conflict 衝突會直接 commit。若需要解決衝突則會再多一個 commit。
git merge --squash <branch_name> 將另一個 branch 的 commit 合併為一筆，特別適合需要做實驗的 fixes bug 或 new feature，最後只留結果。合併完不會幫你先 commit。
git cherry-pick 321d76f 只合併特定其中一個 commit。如果要合併多個，可以加上 -n 指令就不會先幫你 commit，這樣可以多 pick幾個要合併的 commit，最後再 git commit 即可。
git commit的文件太大导致push失败解决方法
Lizejin961019的博客
03-09 4209
1、查看报错日志，找到那个大文件。 Counting objects: 15, done. Delta compression using up to 8 threads. Compressing objects: 100% (14/14), done. Writing objects: 100% (15/15), 382.90 MiB | 1.88 MiB/s, done. Total 15 (delta 8), reused 0 (delta 0) remote: Resolving deltas: 1
Git 使用过程中出现的BUG
SuperLi
07-02 1万+
Git 使用过程中出现的BUG 卡住时的日志打印 Superli-2:ffmpeg-leaning heli$ git push origin master Username for 'https://github.com': MrHeLi Password for 'https://MrHeLi@github.com': Counting objects: 11, done. De...
别再死记硬背Apriori了！用Python手写FP-Growth算法，5步搞定购物篮分析
最新发布
weixin_33738578的博客
05-21 232
本文详细介绍了如何使用Python手写FP-Growth算法进行高效的购物篮分析，相比传统的Apriori算法，FP-Growth通过FP树和分治策略显著提升了性能。文章包含5个核心步骤：从数据预处理到FP树构建，再到频繁项集挖掘，最后通过实战案例验证算法效果，帮助读者快速掌握这一高效算法。
Push fail Enumerating objects: 43, done. Delta compression using up to 8 threads Total 32 (delta 1
17902的博客
07-17 7024
Push fail        Enumerating objects: 43, done.        Delta compression using up to 8 threads        Total 32 (delta 11), reused 0 (delta 0), pack-reu
git一次push异常
imyar
04-28 7193
$ git push -u origin master -f Counting objects: 1265, done. Delta compression using up to 4 threads. Compressing objects: 100% (1166/1166), done. Writing objects: 100% (1265/1265), 53.01 MiB | 38
Git问题集锦（3）
竹枫i的博客
04-28 1141
error：change xxx close Counting objects: 132, done. Delta compression using up to 4 threads. Compressing objects: 100% (16/16), done. Writing objects: 100% (20/20), 1.66 KiB | 0 bytes/s, done. Total 2...
Git使用详细教程
热门推荐
Freewind的专栏
03-23 17万+
一：Git是什么？ 　　Git是目前世界上最先进的分布式版本控制系统。 　　二：SVN与Git的最主要的区别？ 　　SVN是集中式版本控制系统，版本库是集中放在中央服务器的，而干活的时候，用的都是自己的电脑，所以首先要从中央服务器哪里得到最新的版本，然后干活，干完后，需要把自己做完的活推送到中央服务器。集中式版本控制系统是必须联网才能工作，如果在局域网还可以，带宽够大，速度够快，如果在互联网...
Git & TortoiseGit 详细安装使用教程
m0_37383484的博客
04-20 3万+
Git 工具详细安装教程，TortoiseGit 工具详细安装使用教程。
Git学习——简单易懂的教程
自由奔跑的风
07-29 1万+
安装Git Git的下载地址：Git官网下载地址 Git本地仓库和命令 配置用户 下载完Git后，右键会有一个Git Bash here的选项，点击后会弹出一个类似于命令行的窗口： 在此输入此命令配置用户名和邮箱： $ git config --global user.name &amp;amp;amp;amp;amp;quot;Your Name&amp;amp;amp;amp;amp;quot; $ git config --global user.email &
Git 详细安装教程（保姆级详细教程）
Siobhan_Mxin的博客
09-28 3万+
打开 [git官网]，下载git对应操作系统的版本。所有东西下载慢的话就可以去找镜像！​​​Windows系统Git安装教程
Ubuntu18.04更新Git版本并更改命令行中文显示为英文
m0_60630925的博客
12-27 825
注：若/etc/default/locale里的语言不是我们所设置的语言，那么我们在每次对话中使用source /etc/default/locale都可以将这次对话设置为/etc/default/locale里默认的语言。但是根据我的实践，我进行了一些更改，因为参考教程运行并不顺利，只是提供一个思路。笔者之前下载的默认的Git版本为2.17.1，直接更新至最新的版本。因为需要用到git switch的命令，所以要更新Git的版本。3. 在打开的文件中，在文件最后添加以下几行来设置语言环境变量。
Mac Git 命令中文提示切换为英文
TCatTime的博客
07-16 2795
将Mac Git命令的中文提示切换为英文提示。
Mac git 中文提示改为英文
hedeqiang
06-18 1065
最近重装了下 Mac 使用 brew 安装了 Git 、发现命令行下 Git 的提示都是中文、看着非常别扭，然后 Google 了下，找到解决方案 普通命令行 echo "alias git='LANG=en_GB git'" >> ~/.bashrc 安...
下载C4中文/英文数据集【中文文件：186G】【英文文件：305G】
u013250861的博客
08-25 898
下载中文命令：git lfs pull --include "multilingual/c4-zh.*.json.gz"下载英文命令：git lfs pull --include "en/*"3. 安装完成后打开git桌面应应用图标 git bash， 如下图1。6. 运行成功后会创建c4文件夹，及相应的子文件夹和相关文件。7. 下载指定的文件，可使用正则表达式，下载测试文件如下图1。$ cd /d/数据/英语/训练集/训练集重新整理。运行cd c4命令，进入c4文件夹。扩展应用 lfs， 软件下载地址。
如何在Git历史中抹掉中文信息并翻译成英文
污斑兔的博客。
04-10 702
在Git中修改历史记录是一项需要谨慎操作的任务，尤其是在多人协作的项目中。通过使用rebase​或​命令，我们可以有效地抹掉历史中的中文信息，并将其翻译成英文。然而，这些操作会改变Git历史，因此在进行之前务必做好备份，并通知团队成员。希望本文提供的解决方案能够帮助你顺利地处理Git历史中的中文信息问题，保持代码库的整洁和一致性。
Git使用流程及技巧 - 详细教程
NSJim的博客
08-01 6648
本篇文章以GitHub为例，系统为Windows系统。内容详细，包含各种初学者可能会遇到的问题和解决方案。既适合初学者，也适合有一定基础的用户。 文章内容为：本地库及远程库使用流程，设置多个SSH key，局域网内搭建Git远程仓库，合并冲突，减少冲突，撤销更改，版本回退，设置忽略规则（配置gitignore文件），配置gitattributes文件，使用rebase合并分支，IDE集成Git的使用流程，提升SSH传输速度，解决Git Bash命令行的中文乱码问题，解决换行符的替换问题，等等。
Windows安装git 详细教程
weixin_44485316的博客
11-11 1万+
在这个数字化时代，版本控制对于开发者来说至关重要，而Git无疑是其中的佼佼者。无论你是编程新手还是资深开发者，掌握Git都能极大地提升你的工作效率和团队协作体验。本文针对Windows从下载Git安装包、执行安装程序，到验证安装成功，每一步都配以详细截图和说明，确保即便是技术小白也能轻松搞定。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值