{"id":13601925,"url":"https://github.com/angular-schule/angular-cli-ghpages","last_synced_at":"2025-05-14T01:03:27.250Z","repository":{"id":7005937,"uuid":"55674276","full_name":"angular-schule/angular-cli-ghpages","owner":"angular-schule","description":"🚀 Deploy your 🅰️Angular app to GitHub pages, Cloudflare Pages or any other Git repo directly from the Angular CLI! Available on NPM.","archived":false,"fork":false,"pushed_at":"2024-10-23T06:42:25.000Z","size":5822,"stargazers_count":973,"open_issues_count":9,"forks_count":98,"subscribers_count":24,"default_branch":"main","last_synced_at":"2025-04-03T05:47:31.352Z","etag":null,"topics":["angular","angular-cli","angular-cli-ghpages","circle-ci","cloudflare-pages","gh-pages","github-actions","github-pages","ng-deploy","travis-ci"],"latest_commit_sha":null,"homepage":"https://www.npmjs.com/package/angular-cli-ghpages","language":"TypeScript","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/angular-schule.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2016-04-07T07:42:30.000Z","updated_at":"2025-04-01T17:38:36.000Z","dependencies_parsed_at":"2024-05-03T14:52:22.706Z","dependency_job_id":"142ed659-2661-4c72-91f5-4f4e87ad1966","html_url":"https://github.com/angular-schule/angular-cli-ghpages","commit_stats":{"total_commits":228,"total_committers":28,"mean_commits":8.142857142857142,"dds":"0.22807017543859653","last_synced_commit":"5433e40fe788bac51decdcb54adc5243eab336d8"},"previous_names":[],"tags_count":38,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/angular-schule%2Fangular-cli-ghpages","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/angular-schule%2Fangular-cli-ghpages/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/angular-schule%2Fangular-cli-ghpages/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/angular-schule%2Fangular-cli-ghpages/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/angular-schule","download_url":"https://codeload.github.com/angular-schule/angular-cli-ghpages/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":248201652,"owners_count":21064165,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["angular","angular-cli","angular-cli-ghpages","circle-ci","cloudflare-pages","gh-pages","github-actions","github-pages","ng-deploy","travis-ci"],"created_at":"2024-08-01T18:01:10.201Z","updated_at":"2025-04-10T10:46:45.384Z","avatar_url":"https://github.com/angular-schule.png","language":"TypeScript","readme":"# angular-cli-ghpages\n\n[![NPM version][npm-image]][npm-url]\n[![GitHub Actions](https://github.com/angular-schule/angular-cli-ghpages/actions/workflows/main.yml/badge.svg)](https://github.com/angular-schule/angular-cli-ghpages/actions/workflows/main.yml)\n[![The MIT License](https://img.shields.io/badge/license-MIT-orange.svg?color=blue\u0026style=flat-square)](http://opensource.org/licenses/MIT)\n\n**Deploy your Angular app to GitHub Pages, Cloudflare Pages or any other Git repo directly from the Angular CLI! 🚀**\n\n![Screenshot](docs/img/angular-cli-ghpages-deploy.gif)\n\n**Table of contents:**\n\n1. [📖 Changelog](#changelog)\n2. [⚠️ Prerequisites](#prerequisites)\n3. [🚀 Quick Start (local development)](#quickstart-local)\n4. [⚙️ Installation](#installation)\n5. [🚀 Continuous Delivery](#continuous-delivery)\n6. [📦 Deployment Options](#options)\n   - [--base-href](#base-href)\n   - [--build-target](#build-target)\n   - [--no-build](#no-build)\n   - [--repo](#repo)\n   - [--message](#message)\n   - [--branch](#branch)\n   - [--name \u0026 --email](#name)\n   - [--no-dotfiles](#no-dotfiles)\n   - [--no-notfound](#no-notfound)\n   - [--no-nojekyll](#no-nojekyll)\n   - [--cname](#cname)\n   - [--add](#add)\n   - [--dry-run](#dry-run)\n7. [📁 Configuration File](#configuration-file)\n8. [🌍 Environments](#environments)\n9. [⁉️ FAQ](#faq)\n\n\u003chr\u003e\n\n## 📖 Changelog \u003ca name=\"changelog\"\u003e\u003c/a\u003e\n\nA detailed changelog is available in the [releases](https://github.com/angular-schule/angular-cli-ghpages/releases) section.\n\n**⚠️ BREAKING CHANGE (v2)**\n\nThe internal build of Angular has changed with Angular 17.\nUnfortunately, there are now a lot of different _build targets_ and builders.\nWe will try to guess the correct build target, based on the usual conventions to name them.\nThe conventions are shown below, try to specify the build target more and more explicitly until the project compiles.\n\nIn the following example, your app is called `test` and you want to deploy the `production` build.\n\n```bash\nng deploy\n```\n\nIf this doesn't work, try this:\n\n```bash\nng deploy --build-target=test\n```\n\nIf this doesn't work, try this:\n\n```bash\nng deploy --build-target=test:build:production\n```\n\nYou can also and modify your `angular.json` to archive the same:\n\n```json\n{\n  \"deploy\": {\n    \"builder\": \"angular-cli-ghpages:deploy\",\n    \"options\": {\n      \"buildTarget\": \"test:build:production\"\n    }\n  }\n}\n```\n\nFor your convenience, you can also use `prerenderTarget` (which adds the suffix `:prerender:production`).\nThere is no support for `universalBuildTarget` or `serverTarget` because GitHub Pages only supports static assets and no Server-Side Rendering!\n\nWe will then try to deploy the `dist/test/browser` folder to GitHub Pages.\nIf this is not the folder that you want to serve, you should explicitly specify the directory with the `--dir` option:\n\n```bash\nng deploy --dir=dist/test/browser\n```\n\nThis new build logic is a breaking change, therefore `angular-cli-ghpages` v2 only supports Angular 17 and higher.\nFor previous versions of Angular, use `angular-cli-ghpages` v1.x.\n\n## ⚠️ Prerequisites \u003ca name=\"prerequisites\"\u003e\u003c/a\u003e\n\nThis command has the following prerequisites:\n\n- Git 1.9 or higher (execute `git --version` to check your version)\n- Angular project created via [Angular CLI](https://github.com/angular/angular-cli) v17 or greater\n- older Angular projects can still use a v1.x version or use the standalone program. See the documentation at [README_standalone](https://github.com/angular-schule/angular-cli-ghpages/blob/master/docs/README_standalone.md).\n\n## 🚀 Quick Start (local development) \u003ca name=\"quickstart-local\"\u003e\u003c/a\u003e\n\nThis quick start assumes that you are starting from scratch.\nIf you already have an existing Angular project on GitHub, skip step 1 and 2.\n\n1. Install the latest version of the Angular CLI globally\n   and create a new Angular project.\n\n   ```sh\n   npm install -g @angular/cli\n   ng new your-angular-project --defaults\n   cd your-angular-project\n   ```\n\n2. By default, the Angular CLI initializes a Git repository for you.  \n   To add a new remote for GitHub, use the `git remote add` command:\n\n   ```sh\n   git remote add origin https://github.com/\u003cusername\u003e/\u003crepositoryname\u003e.git\n   ```\n\n   Hints:\n\n   - Create a new empty GitHub repository first.\n   - Replace `\u003cusername\u003e` and `\u003crepositoryname\u003e` with your username from GitHub and the name of your new repository.\n   - Please enter the URL `https://github.com/\u003cusername\u003e/\u003crepositoryname\u003e.git` into your browser – you should see your existing repository on GitHub.\n   - Please double-check that you have the necessary rights to make changes to the given project!\n\n3. Add `angular-cli-ghpages` to your project. For details, see the [installation section](#installation).\n\n   ```sh\n   ng add angular-cli-ghpages\n   ```\n\n4. Deploy your project to GitHub pages with all default settings.\n   Your project will be automatically built in production mode.\n\n   ```sh\n   ng deploy --base-href=/\u003crepositoryname\u003e/\n   ```\n\n   Which is the same as:\n\n   ```sh\n   ng deploy your-angular-project --base-href=/\u003crepositoryname\u003e/\n   ```\n\n   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.\n\n5. Your project should be available at `https://\u003cusername\u003e.github.io/\u003crepositoryname\u003e`.  \n   Learn more about GitHub pages on the [official website](https://pages.github.com/).\n\n## ⚙️ Installation \u003ca name=\"installation\"\u003e\u003c/a\u003e\n\n`angular-cli-ghpages` can be installed via `ng add`.\nThis will install the NPM package and add the necessary `deploy` configuration to your `angular.json` file.\n\n```sh\nng add angular-cli-ghpages\n```\n\nIf you have multiple projects in one workspace, you should manually define the project name:\n\n```sh\nng add angular-cli-ghpages --project MYPROJECTNAME\n```\n\n## 🚀 Continuous Delivery \u003ca name=\"continuous-delivery\"\u003e\u003c/a\u003e\n\nIf you run this command from a CI/CD environment, the deployment will most likely not work out of the box.\nFor security reasons, those environments usually have read-only privileges, or you haven't set up Git correctly.\nTherefore, you should take a look at [\"personal access tokens\" `GH_TOKEN`](https://help.github.com/articles/creating-an-access-token-for-command-line-use/) (which works everywhere) and the [\"installation access token\" `GITHUB_TOKEN`](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token) (which is exclusively provided by GitHub actions).\nIn short: a token replaces username and password and is a safer choice because a token can be revoked at any time.\n\nAll you need to do is to set an environment variable called `GH_TOKEN` (or `PERSONAL_TOKEN`) in your CI/CD environment.\nFor GitHub Actions, you can also use the `GITHUB_TOKEN` which provides more security and requires no additional setup.\nAll the tokens only work if the remote repository uses the HTTPS scheme.\nTokens are generally not supported for Git over SSH.\n\nIf the current working directory is already a git repository, you don't need to specify the repository again. The current remote repository with the name `origin` will be used in this case.\nYou can also override the repository setting using the `--repo` option.\n\nIf you specify all the three options (`--repo`, `--name` and `--email`), then angular-cli-ghpages will also work in directories that are not under version control at all.\n\n```sh\nng deploy --repo=https://github.com/\u003cusername\u003e/\u003crepositoryname\u003e.git --name=\"Your Git Username\" --email=your.mail@example.org\n```\n\n(replace `\u003cusername\u003e` and `\u003crepositoryname\u003e` with your username from GitHub and the name of your repository)\n\n\u003e **ℹ️ Note for GitHub Actions**\n\u003e\n\u003e The `GITHUB_TOKEN` (installation access token) will only trigger a release of a new website if the action runs in a private repository. In a public repo, a commit is generated, but the site does not change. See this [GitHub Community post](https://github.community/t5/GitHub-Actions/Github-action-not-triggering-gh-pages-upon-push/m-p/26869) for more info. If your repo is public, you must still use the `GH_TOKEN` (personal access token).\n\n## 📦 Deployment Options \u003ca name=\"options\"\u003e\u003c/a\u003e\n\n#### --base-href \u003ca name=\"base-href\"\u003e\u003c/a\u003e\n\n- **optional**\n- Default: `undefined` (string)\n- Example:\n  - `ng deploy` – The tag `\u003cbase href=\"/\"\u003e` remains unchanged in your `index.html`\n  - `ng deploy --base-href=/the-repositoryname/` – The tag `\u003cbase href=\"/the-repositoryname/\"\u003e` is added to your `index.html`\n\nSpecify the base URL for the application being built.\nSame as `ng build --base-href=/XXX/`\n\n**ℹ️ Please read the next lines carefully, or you will get 404 errors in case of a wrong configuration!**\n\n##### A) You don't want to use a custom domain\n\nIf you don't want to use an own domain, then your later URL of your hosted Angular project should look like this:\n`https://your-username.github.io/the-repositoryname`.\nIn this case you have to adjust the `--base-href` accordingly:\n\n```sh\nng deploy --base-href=/the-repositoryname/\n```\n\n##### B) You want to use a custom domain\n\nIf you want to use your own domain, then you don't have to adjust `--base-href`.\nHowever, it is now necessary to set the `--cname` parameter!\n\n```sh\nng deploy --cname=example.org\n```\n\nSee the option [--cname](#cname) for more information!\n\n#### --build-target \u003ca name=\"build-target\"\u003e\u003c/a\u003e\n\n- **optional**\n- Default: `undefined` (string)\n- Example:\n  - `ng deploy` – Angular project is built in `production` mode\n  - `ng deploy --build-target=test` – Angular project is using the build configuration `test` (this configuration must exist in the `angular.json` file)\n\nIf no `buildTarget` is set, the `production` build of the default project will be chosen.\nThe `buildTarget` simply points to an existing build configuration for your project, as specified in the `configurations` section of `angular.json`.\nMost projects have a default configuration and a production configuration (commonly activated by using the `--prod` flag) but it is possible to specify as many build configurations as needed.\n\nThis is equivalent to calling the command `ng build --configuration=XXX`.\nThis command has no effect if the option `--no-build` is active.\n\n**⚠️ BREAKING CHANGE (v1)**\n\nThis option was called `--configuration` in previous versions.\n\nBEFORE (_does not work_):\n\n```\nng deploy --configuration=test\n```\n\nNOW:\n\n```\nng deploy --build-target=test\n```\n\n#### --no-build \u003ca name=\"no-build\"\u003e\u003c/a\u003e\n\n- **optional**\n- Default: `false` (string)\n- Example:\n  - `ng deploy` – Angular project is build in production mode before the deployment\n  - `ng deploy --no-build` – Angular project is NOT build\n\nSkip the build process during deployment.\nThis can be used when you are sure that you haven't changed anything and want to deploy with the latest artifact.\nThis command causes the `--build-target` setting to have no effect.\n\n#### --repo \u003ca name=\"repo\"\u003e\u003c/a\u003e\n\n- **optional**\n- Default: URL of the origin remote of the current dir (assumes a Git repository)\n- Example: `ng deploy --repo=https://github.com/\u003cusername\u003e/\u003crepositoryname\u003e.git`\n\nThis specifies the target repository. If none is given as an option, the repository is discovered from the current working directory.\n\nBy default, this command assumes that the current working directory is a Git repository,\nand that you want to push changes to the `origin` remote.\nIf instead, your files are not in a git repository, or if you want to push to another repository,\nyou can provide the repository URL in the `repo` option.\n\n\u003e **ℹ️ Hint**\n\u003e\n\u003e Set an environment variable with the name `GH_TOKEN` / `PERSONAL_TOKEN` or `GITHUB_TOKEN` and it will be automatically added to the URL, if it uses the HTTPS shema (it must start with `https://github.com`).\n\u003e Tokens are generally not supported for Git over SSH (starts with `git@github.com`).\n\nLearn more about [\"personal access tokens\" here](https://help.github.com/articles/creating-an-access-token-for-command-line-use/) (`GH_TOKEN`) and about the [\"installation access token\" here](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token) (`GITHUB_TOKEN`). `PERSONAL_TOKEN` is an alias for `GH_TOKEN`.\n\n#### --message \u003ca name=\"message\"\u003e\u003c/a\u003e\n\n- **optional**\n- Default: `Auto-generated commit` (string)\n- Example: `ng deploy --message=\"What could possibly go wrong?\"`\n\nThe commit message **must be wrapped in quotes** if there are any spaces in the text.  \nSome additional text is always added to the message, if the command runs on Travis CI, Circle CI or GitHub Actions.\n\n#### --branch \u003ca name=\"branch\"\u003e\u003c/a\u003e\n\n- **optional**\n- Default: `gh-pages` (string)\n- Example: `ng deploy --branch=master`\n\nThe name of the branch you'll be pushing to.\nThe default uses GitHub's `gh-pages` branch,\nbut this can be configured to push to any branch on any remote.\nYou have to change this to `master` if you are pushing to a GitHub organization page (instead of a GitHub user page).\n\n#### --name \u0026 --email \u003ca name=\"name\"\u003e\u003c/a\u003e\n\n- **optional**\n- Default: value of `git config user.name` and `git config user.email`\n- Example: `ng deploy --name=\"Displayed Username\" --email=mail@example.org`\n\nIf you run the command in a repository without `user.name` or `user.email` Git config properties\n(or on a machine without these global config properties),\nyou must provide user info before Git allows you to commit.\nIn this case, provide **both** `name` and `email` string values to identify the committer.\n\n#### --no-dotfiles \u003ca name=\"no-dotfiles\"\u003e\u003c/a\u003e\n\n- **optional**\n- Default: Dotfiles are created (boolean `true`)\n- Example:\n  - `ng deploy` – Dotfiles are included by default.\n  - `ng deploy --no-dotfiles` – Dotfiles are ignored.\n\nThe command includes dotfiles by default (e.g. `.htaccess` will be committed).\nWith `--no-dotfiles` files starting with `.` are ignored.\n\n#### --no-notfound \u003ca name=\"no-notfound\"\u003e\u003c/a\u003e\n\n- **optional**\n- Default: `404.html` file is created (boolean `true`)\n- Example:\n  - `ng deploy` – A `404.html` file is created by default.\n  - `ng deploy --no-notfound` – No `404.html` file is created.\n\nBy default, a `404.html` file is created, because this is the only known workaround to avoid 404 error messages on GitHub Pages.\nFor Cloudflare Pages we highly recommend to disable the `404.html` file by setting this switch to true! \nSee [#178](https://github.com/angular-schule/angular-cli-ghpages/issues/178)\n\n#### --no-nojekyll \u003ca name=\"no-nojekyll\"\u003e\u003c/a\u003e\n\n- **optional**\n- Default: `.nojekyll` file is created (boolean `true`)\n- Example:\n  - `ng deploy` – A `.nojekyll` file is created by default.\n  - `ng deploy --no-nojekyll` – No `.nojekyll` file is created.\n\nBy default, a `.nojekyll` file is created, because we assume you don't want to compile the build again with Jekyll.\n\n**Explanation:**\nBy creating such a file in the root of your pages repo, you will bypass the Jekyll static site generator on GitHub Pages.\nStatic content is still delivered – even without Jekyll.\nBut now the deployment will be a bit faster.\nThis is also necessary if your site uses files or directories that start with **\\_underscores** since Jekyll considers these to be special resources and does not copy them to the final site.\nThe same applies to `.txt` files in your assets folder: They will just disappear if Jekyll processes the build. see [#160](https://github.com/angular-schule/angular-cli-ghpages/issues/160)\n\n#### --cname \u003ca name=\"cname\"\u003e\u003c/a\u003e\n\n- **optional**\n- Default: `undefined` (string) – No CNAME file is generated\n- Example:\n  - `ng deploy --cname=example.com`\n\nA CNAME file will be created enabling you to use a custom domain.\n[More information on GitHub Pages using a custom domain](https://help.github.com/articles/using-a-custom-domain-with-github-pages/).\n\n#### --add \u003ca name=\"add\"\u003e\u003c/a\u003e\n\n- **optional**\n- Default: `false` (boolean) – The existing files will be removed from the branch you'll be pushing to as expected.\n- Example:\n  - `ng deploy --add=true`\n\nIf is set to `true`, it will only add, and never remove existing files.\nBy default, existing files in the target branch are removed before adding the ones.\n[More information](https://www.npmjs.com/package/gh-pages#optionsadd).\n\n#### --dir \u003ca name=\"dir\"\u003e\u003c/a\u003e\n\n- **optional**\n- Default: `undefined` (string) – Conventions will be used to guess the correct directory in your `dist` folder.\n- Example:\n  - `ng deploy --dir=dist/completely-different-folder/en`\n\nOverrides the directory for all published sources, relative to the current working directory.\n\n#### --dry-run \u003ca name=\"dry-run\"\u003e\u003c/a\u003e\n\n- **optional**\n- Default: `false` (boolean)\n- Example:\n  - `ng deploy` – Normal behavior: Changes are applied.\n  - `ng deploy --dry-run` – No changes are applied at all.\n\nRun through without making any changes.\nThis can be very useful because it outputs what would happen without doing anything.\n\n## 📁 Configuration File \u003ca name=\"configuration-file\"\u003e\u003c/a\u003e\n\nTo avoid all these command-line cmd options, you can write down your configuration in the `angular.json` file in the `options` attribute of your deploy project's architect. Just change the kebab-case to lower camel case. This is the notation of all options in lower camel case:\n\n- baseHref\n- buildTarget\n- noBuild\n- repo\n- message\n- branch\n- name\n- email\n- noDotfiles\n- noNotfound\n- noNojekyll\n- cname\n- dir\n- dryRun\n\nA list of all available options is also available [here](https://github.com/angular-schule/angular-cli-ghpages/blob/master/src/deploy/schema.json).\n\nExample:\n\n```sh\nng deploy --base-href=https://angular-schule.github.io/angular-cli-ghpages/ --name=\"Angular Schule Team\" --email=team@angular.schule\n```\n\nbecomes\n\n```json\n\"deploy\": {\n  \"builder\": \"angular-cli-ghpages:deploy\",\n  \"options\": {\n    \"baseHref\": \"https://angular-schule.github.io/angular-cli-ghpages/\",\n    \"name\": \"Angular Schule Team\",\n    \"email\": \"team@angular.schule\"\n  }\n}\n```\n\nNow you can just run `ng deploy` without all the options in the command line! 😄\n\n\u003e **ℹ️ Hint**\n\u003e\n\u003e You can always use the [--dry-run](#dry-run) option to verify if your configuration is right.\n\u003e The project will build but not deploy.\n\n## 🌍 Environments \u003ca name=\"environments\"\u003e\u003c/a\u003e\n\nWe have seen `angular-cli-ghpages` running on various environments, like Travis CI, CircleCi or GitHub Actions.\nPlease share your knowledge by writing an article about how to set up the deployment.\n\n1. [GitHub Actions](https://angular.schule/blog/2020-01-everything-github)\n2. Travis CI\n3. CircleCI\n\n## ⁉️ FAQ \u003ca name=\"faq\"\u003e\u003c/a\u003e\n\nBefore posting any issue, [please read the FAQ first](https://github.com/angular-schule/angular-cli-ghpages/wiki/FAQ).\nSee the contributors documentation at [README_contributors](https://github.com/angular-schule/angular-cli-ghpages/blob/master/docs/README_contributors.md) if you want to debug and test this project.\n\n## License \u003ca name=\"license\"\u003e\u003c/a\u003e\n\nCode released under the [MIT license](LICENSE).\n\n\u003chr\u003e\n\n\u003cimg src=\"https://assets.angular.schule/logo-angular-schule.png\" height=\"60\"\u003e\n\n### \u0026copy; 2017-2024 https://angular.schule\n\nThis project is made on top of [tschaub/gh-pages](https://github.com/tschaub/gh-pages).  \nThank you very much for this great foundation!\n\n[npm-url]: https://www.npmjs.com/package/angular-cli-ghpages\n[npm-image]: https://badge.fury.io/js/angular-cli-ghpages.svg\n","funding_links":[],"categories":["angular","Angular"],"sub_categories":["Deployment"],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fangular-schule%2Fangular-cli-ghpages","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fangular-schule%2Fangular-cli-ghpages","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fangular-schule%2Fangular-cli-ghpages/lists"}