-
Notifications
You must be signed in to change notification settings - Fork 0
26 lines (26 loc) · 1.57 KB
/
main.yml
File metadata and controls
26 lines (26 loc) · 1.57 KB
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
# This is a basic workflow to help you get started with Actions
name: Build and Deploy
# Controls when the workflow will run
on:
# Triggers the workflow on push or pull request events but only for the master branch
push:
branches: [ master ]
# 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
# Runs a single command using the runners shell
- name: Deploy by gh-pages
uses: AhsanAyaz/angular-deploy-gh-pages-actions@v1.3.2 ## replace by latest version without it you will see Expected format {org}/{repo}[/path]@ref. Actual 'AhsanAyaz/angular-deploy-gh-pages-actions',Input string was not in a correct format.
with:
github_access_token: ${{ secrets.ACCESS_TOKEN }} # see the Configuration section for how you can create secrets
build_configuration: production # The build environment for the app. Please look configurations in your angular.json
base_href: /angular/ # make sure this corresponds to https://<your_username>.github.io/<base_href>/
deploy_branch: gh-pages # The branch the action should deploy to.
angular_dist_build_folder: dist/freecell-demo # The folder where your project is supposed to be after running ng build by the action.