You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ved ny release, f.eks., vil det være mest hensiktsmessig at kun Docker-image som er endret får en ny release-tag. Mulig dorny/path-filter kunne vært brukt.
Noe ala dette:
jobs:
# JOB to run change detectionchanges:
runs-on: ubuntu-latest# Required permissionspermissions:
pull-requests: readoutputs:
# Expose matched filters as job 'packages' output variablepackages: ${{ steps.filter.outputs.changes }}steps:
# For pull requests it's not necessary to checkout the code
- uses: dorny/paths-filter@v3id: filterwith:
filters: | package1: src/package1 package2: src/package2# JOB to build and test each of modified packagesbuild:
needs: changesstrategy:
matrix:
# Parse JSON array containing names of all filters matching any of changed files# e.g. ['package1', 'package2'] if both package folders contains changespackage: ${{ fromJSON(needs.changes.outputs.packages) }}runs-on: ubuntu-lateststeps:
- uses: actions/checkout@v4
- ...
The text was updated successfully, but these errors were encountered:
Ved ny release, f.eks., vil det være mest hensiktsmessig at kun Docker-image som er endret får en ny release-tag. Mulig dorny/path-filter kunne vært brukt.
Noe ala dette:
The text was updated successfully, but these errors were encountered: