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: CONTRIBUTING.md
+32Lines changed: 32 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,6 +57,38 @@ The first-time build takes several minutes (Oracle image pull +
57
57
Instant Client setup + `bundle install`). Subsequent starts of the
58
58
same Codespace are much faster.
59
59
60
+
#### Stopping and restarting your Codespace
61
+
62
+
Codespaces are billed for compute time while they are running, and for
63
+
storage while they are stopped. Stop your Codespace when you take a
64
+
break so you are not billed for an idle machine; your files, installed
65
+
gems, and Oracle Database state are preserved across stop/start. See
66
+
GitHub's documentation on [stopping and starting a codespace](https://docs.github.com/en/codespaces/developing-in-a-codespace/stopping-and-starting-a-codespace)
67
+
for full details.
68
+
69
+
Ways to stop a Codespace:
70
+
71
+
-**From the GitHub web UI** — go to <https://github.com/codespaces>,
72
+
click the **⋯** menu next to the Codespace, and choose **Stop
73
+
codespace**.
74
+
-**From the VS Code Command Palette** (browser or desktop, while
75
+
connected to the Codespace) — run **Codespaces: Stop Current
76
+
Codespace**.
77
+
-**From the `gh` CLI** — `gh codespace stop` (interactive picker) or
78
+
`gh codespace stop -c <codespace-name>`. List your Codespaces with
79
+
`gh codespace list`.
80
+
81
+
Codespaces also stop automatically after a period of inactivity (30
82
+
minutes by default). You can change the timeout under
0 commit comments