|
| 1 | +# This is a basic workflow to help you get started with Actions |
| 2 | + |
| 3 | +name: Build and Deploy to Github Pages |
| 4 | + |
| 5 | +# Controls when the workflow will run |
| 6 | +on: |
| 7 | + # Triggers the workflow on push or pull request events but only for the master branch |
| 8 | + push: |
| 9 | + branches: [ master ] |
| 10 | + |
| 11 | + # Allows you to run this workflow manually from the Actions tab |
| 12 | + workflow_dispatch: |
| 13 | + |
| 14 | +# A workflow run is made up of one or more jobs that can run sequentially or in parallel |
| 15 | +jobs: |
| 16 | + # This workflow contains a single job called "build" |
| 17 | + build: |
| 18 | + # The type of runner that the job will run on |
| 19 | + runs-on: ubuntu-latest |
| 20 | + strategy: |
| 21 | + matrix: |
| 22 | + node-version: [16.x] |
| 23 | + base_href: [vagas-java] |
| 24 | + # Steps represent a sequence of tasks that will be executed as part of the job |
| 25 | + steps: |
| 26 | + # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it |
| 27 | + - uses: actions/checkout@v2 |
| 28 | + |
| 29 | + - name: Angular Deploy gh-pages Actions |
| 30 | + # You may pin to the exact commit or the version. |
| 31 | + # uses: AhsanAyaz/angular-deploy-gh-pages-actions@0e4f1a953d00116ca38fbf1bcdb37f91923015ef |
| 32 | + |
| 33 | + with: |
| 34 | + # Github access token token used to deploy on gh_pages. You can find it on Github. |
| 35 | + github_access_token: ${{ secrets.GITHUB_TOKEN }} |
| 36 | + # The directory of the angular project, in which all the commands will run. It's optional, default is ./ |
| 37 | + angular_project_dir: ./codigofonte/ionicv4/soujavaVagas/ |
| 38 | + # Build configuration for the angular app |
| 39 | + build_configuration: production # optional, default is production |
| 40 | + # base href for the app |
| 41 | + base_href: /${{ matrix.base_href }}/ # optional, default is / |
| 42 | + # branch on which the angular build will be deployed |
| 43 | + deploy_branch: gh-pages # optional, default is gh-pages |
| 44 | + # The folder in which `ng build` provides its output. This is the folder which will be deployed to the `deploy_branch`. |
| 45 | + angular_dist_build_folder: dist/${{ matrix.base_href }} # optional, default is dist |
| 46 | + # If the action should run 'ng lint' |
| 47 | + # run_lint: # optional |
| 48 | + # Will not fail the step if anything fails |
| 49 | + # skip_failure: # optional |
0 commit comments