-
Notifications
You must be signed in to change notification settings - Fork 0
44 lines (38 loc) · 1.78 KB
/
main.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
# This is a basic workflow to help you get started with Actions
name: CI
# Controls when the action will run.
on:
# Triggers the workflow on push or pull request events but only for the master branch
push:
branches: [ master ]
pull_request:
branches: [ master ]
# Allows you to run this workflow manually from the Actions tab
workflow_dispatch:
# A workflow run is made up of one or more jobs that can run sequentially or in parallel
jobs:
# This workflow contains a single job called "build"
build:
# The type of runner that the job will run on
runs-on: ubuntu-latest
# Steps represent a sequence of tasks that will be executed as part of the job
steps:
# Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
- uses: actions/checkout@v2
- name: Angular Deploy gh-pages Actions
# You may pin to the exact commit or the version.
# uses: AhsanAyaz/angular-deploy-gh-pages-actions@0e4f1a953d00116ca38fbf1bcdb37f91923015ef
uses: AhsanAyaz/angular-deploy-gh-pages-actions@v1.3.2
with:
# Github access token token used to deploy on gh_pages. You can find it on Github.
github_access_token: ${{ secrets.ACCESS_TOKEN }}
# The directory of the angular project, in which all the commands will run
angular_project_dir: ./
# Build configuration for the angular app
build_configuration: production
# base href for the app
base_href: https://ac-uok.com/
# branch on which the angular build will be deployed
deploy_branch: gh-pages
# The folder in which `ng build` provides its output. This is the folder which will be deployed to the `deploy_branch`.
angular_dist_build_folder: dist/Website