You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`status`| ✓ |status| Report the state of working tree |
16
-
|`add`|—|add| Required for each path before making a commit |
17
-
|`commit`|—|commit| Store prepared changes in local revision history |
15
+
|`status`| ✓ || Report the state of working tree |
16
+
|`add`|✓|| Required for each path before making a commit |
17
+
|`commit`|✓|| Store prepared changes in local revision history |
18
18
|`rm`| ✓ |`rm`, `delete`| Prepare paths for deletion in next commit |
19
19
|`mv`| ✓ |`move`| Prepare relocated content for next commit |
20
-
|`branch`|—|| Create local context for commits |
21
-
|`checkout`|—|| Switch branches, or rewrite working tree from commit |
20
+
|`branch`|✓|| Create local context for commits |
21
+
|`checkout`|✓|| Switch branches, or rewrite working tree from commit |
22
22
|`merge`| ✓ || Join branch histories and changes to working tree |
23
-
|`log`|—|| No network required |
23
+
|`log`|✓|| No network required |
24
24
|`clone`| ✗ |`checkout`| Acquire the entire history of a project locally for the first time |
25
25
|`push`| ✗ |`commit`| Upload commit history to GitHub/centralized Git host |
26
26
|`pull`| ✗ || Download and integrate GitHub repository history with local one |
27
27
|`fetch`| ✗ || Download GitHub repository history with no other action |
28
28
29
-
**Key:** ✓ yes, ✗ no, — partial
29
+
**Key:** ✓ yes, ✗ no
30
30
31
31
## Leveraging Git's support of SVN
32
32
During a VCS change, there may be a need to begin using Git locally while the hosted repositories remain under Subversion control. The `git svn` command and sub-commends provide the ability to interact with Subversion's repositories while using all the benefits of Git on the command line or with graphical clients.
0 commit comments