Skip to content

Commit b200c26

Browse files
committed
README points to releases page instead of latest release
Updating the README with every release URL makes the release process error-prone and doesn't offer a lot of practical benefit. Also, remove the curl extract example.
1 parent e6842fe commit b200c26

File tree

1 file changed

+4
-8
lines changed

1 file changed

+4
-8
lines changed

README.md

Lines changed: 4 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -70,14 +70,10 @@ version][5].
7070

7171
### Getting started
7272

73-
1. [Download the latest release][release] and extract:
73+
1. [Download the latest release version][release] and extract *or* clone the
74+
repository using Git:
7475

75-
`curl -L <release-url> | gzip -dc | tar xvf -`
76-
77-
Tip: You can also use Git to obtain the utilities instead, which may make
78-
upgrading to future backup-utils releases easier:
79-
80-
`git clone https://github.com/github/backup-utils.git backup-utils`
76+
`git clone https://github.com/github/backup-utils.git`
8177

8278
2. Copy the [`backup.config-example`][2] file to `backup.config` and modify as
8379
necessary. The `GHE_HOSTNAME` value must be set to the GitHub Enterprise
@@ -92,7 +88,7 @@ version][5].
9288

9389
5. Run `bin/ghe-backup` to perform an initial full backup.
9490

95-
[release]: https://github.com/github/backup-utils/releases/download/v0.9.0/github-backup-utils-v0.9.0.tar.gz
91+
[release]: https://github.com/github/backup-utils/releases
9692

9793
### Using the backup and restore commands
9894

0 commit comments

Comments
 (0)