Skip to content

Adding cmdlet detection #89

Adding cmdlet detection

Adding cmdlet detection #89

Workflow file for this run

# This is a basic workflow to help you get started with Actions
name: Test & Build Module
# 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" ]
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"
WindowsBuild:
# The type of runner that the job will run on
runs-on: windows-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@v3
- name: Test with Pester
shell: pwsh
run: .\PSPublishModule.Tests.ps1
- name: Build Module
shell: pwsh
run: .\Build\Build-Module.ps1
LinuxBuild:
# 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@v3
- name: Test with Pester
shell: pwsh
run: .\PSPublishModule.Tests.ps1
- name: Build Module
shell: pwsh
run: .\Build\Build-Module.ps1
MacOsBuild:
# The type of runner that the job will run on
runs-on: macos-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@v3
- name: Test with Pester
shell: pwsh
run: .\PSPublishModule.Tests.ps1
- name: Build Module
shell: pwsh
run: .\Build\Build-Module.ps1