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
Python scripts are unlikely to be included in your ``$PATH`` by default, this means it cannot be run directly in terminal with ``$ github-backup ...``, you can either add python's install path to your environments ``$PATH`` or call the script directly e.g. using ``$ ~/.local/bin/github-backup``.*
@@ -249,7 +249,7 @@ Note: When you run github-backup, you will be asked whether you want to allow "
249
249
Github Rate-limit and Throttling
250
250
--------------------------------
251
251
252
-
"github-backup" will automatically throttle itself based on feedback from the Github API.
252
+
"github-backup" will automatically throttle itself based on feedback from the Github API.
253
253
254
254
Their API is usually rate-limited to 5000 calls per hour. The API will ask github-backup to pause until a specific time when the limit is reset again (at the start of the next hour). This continues until the backup is complete.
255
255
@@ -325,7 +325,12 @@ Gotchas / Known-issues
325
325
All is not everything
326
326
---------------------
327
327
328
-
The ``--all`` argument does not include: cloning private repos (``-P, --private``), cloning forks (``-F, --fork``), cloning starred repositories (``--all-starred``), ``--pull-details``, cloning LFS repositories (``--lfs``), cloning gists (``--gists``) or cloning starred gist repos (``--starred-gists``). See examples for more.
328
+
The ``--all`` argument does not include: downloading attachments from issue and pull request comments (``--attachments``), cloning private repos (``-P, --private``), cloning forks (``-F, --fork``), cloning starred repositories (``--all-starred``), ``--pull-details``, cloning LFS repositories (``--lfs``), cloning gists (``--gists``) or cloning starred gist repos (``--starred-gists``). See examples for more.
329
+
330
+
Saves nothing if no arguments are passed
331
+
----------------------------------------
332
+
333
+
At least one argument like ``--all`` or ``--repositories`` is needed for github-backup to actually save data. Without relevant arguments, github-backup fetches some data from GitHub but doesn't put any of it into files.
329
334
330
335
Starred repository size
331
336
-----------------------
@@ -363,9 +368,9 @@ This means any blocking errors on previous runs can cause missing data in backup
363
368
364
369
Using (``--incremental-by-files``) will request new data from the API **based on when the file was modified on filesystem**. e.g. if you modify the file yourself you may miss something.
365
370
366
-
Still saver than the previous version.
371
+
Still safer than the previous version.
367
372
368
-
Specifically, issues and pull requests are handled like this.
373
+
Incremental backup only changes how issue and pull request data is fetched.
369
374
370
375
Known blocking errors
371
376
---------------------
@@ -429,27 +434,27 @@ Github Backup Examples
429
434
430
435
Backup all repositories, including private ones using a classic token::
Quietly and incrementally backup useful Github user data (public and private repos with SSH) including; all issues, pulls, all public starred repos and gists (omitting "hooks", "releases" and therefore "assets" to prevent blocking). *Great for a cron job.* ::
0 commit comments