Skip to content

Commit d91a1fc

Browse files
committed
docs: highlight ng deploy auto-discovery feature
1 parent 52add3e commit d91a1fc

1 file changed

Lines changed: 5 additions & 10 deletions

File tree

README.md

Lines changed: 5 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -81,23 +81,18 @@ If you already have an existing Angular project on GitHub, skip steps 1 and 2.
8181
- Please enter the URL `https://github.com/<username>/<repositoryname>.git` into your browser – you should see your existing repository on GitHub.
8282
- Please double-check that you have the necessary rights to make changes to the given project!
8383

84-
3. Add `angular-cli-ghpages` to your project. For details, see the [installation section](#installation).
84+
3. Add `angular-cli-ghpages` to your project. When you run `ng deploy` for the first time, the Angular CLI will prompt you to choose a deployment target – select **angular-cli-ghpages** from the list:
8585

8686
```sh
87-
ng add angular-cli-ghpages
87+
ng deploy
8888
```
8989

90-
4. Deploy your project to GitHub pages with all default settings.
91-
Your project will be automatically built in production mode.
90+
Alternatively, you can install it directly via `ng add angular-cli-ghpages`. See the [installation section](#installation) for details.
9291

93-
```sh
94-
ng deploy --base-href=/<repositoryname>/
95-
```
96-
97-
Which is the same as:
92+
4. Deploy your project to GitHub Pages with all default settings. Your project will be automatically built in production mode.
9893

9994
```sh
100-
ng deploy your-angular-project --base-href=/<repositoryname>/
95+
ng deploy --base-href=/<repositoryname>/
10196
```
10297

10398
Please be aware of the `--base-href` option. It is necessary when your project will be deployed to a non-root folder. See more details below.

0 commit comments

Comments
 (0)