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
Copy file name to clipboardExpand all lines: packages/homepage/content/docs/2-git.md
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,14 +8,13 @@ description:
8
8
9
9
## Base Concept
10
10
11
-
With CodeSandbox you can import any GitHub repositories as a sandbox (this
11
+
With CodeSandbox you can import any GitHub repository as a sandbox (this
12
12
concept is described in more detail [here](/docs/importing#import-from-github)).
13
13
An imported sandbox will automatically stay in sync with the GitHub repository;
14
14
if you make a commit to GitHub it will reflect immediately in the sandbox.
15
15
16
16
For that reason we've made GitHub sandboxes immutable, this means that you
17
-
cannot make direct changes to the sandbox itself. However, you can still fork
18
-
the sandbox. When you create a fork of a GitHub sandbox we will still keep a
17
+
cannot make direct changes to the sandbox itself. They are treated as [templates](/docs/templates), so you can fork from them. When you create a fork of a GitHub sandbox we will still keep a
19
18
reference to the original GitHub repository. This allows you to create commits
20
19
and open pull requests from the forked sandboxes.
21
20
@@ -25,7 +24,7 @@ Anyone can import public GitHub repositories. You need a [Pro subscription](http
25
24
26
25
You can see a forked sandbox of a GitHub sandbox as a separate branch. We still
27
26
keep a reference to the original branch, and we also track the changes that
28
-
happen. When you create a fork of the Git sandbox you will see a new panel in
27
+
happen. When you create a fork of the GitHub sandbox you will see a new panel in
0 commit comments