🚀[Feature]: Only publish if we have changes

[MariusStorhaug]

Description

Only publish if the important files have changes.

Discorvery

• tj-actions/changed-files -> make a custom action? -> Will not run if the framework has changes.
• git diff -> get list of files -> make a custom action? -> Will not run if the framework has changes.
• get hash for published module and the built module -> Will take the result and compare => It will run if there are "external" changes that causes the compiled module to have changed.

[MariusStorhaug]

Resolved via PR #275

This feature has been implemented using automatic file change detection in the Get-PSModuleSettings action.

How It Works

The action automatically detects whether a PR contains changes to "important" files that warrant a new release:

1. Fetches changed files via GitHub API for each PR
2. Matches files against important patterns
3. Sets ReleaseType based on the result:
   • Release - Merged PR to default branch with important changes
   • Prerelease - Open/labeled PR with prerelease label and important changes
   • None - No important changes detected → no version bump, no publish

Important File Patterns

$importantPatterns = @(
    '^src/'
    '^examples/'
    '^README\.md$'
)

Files that trigger releases:

Path	Description
src/**	Module source code
examples/**	Example scripts
README.md	Documentation

Files that do NOT trigger releases:

• .github/workflows/* (all workflow configurations)
• .github/linters/* (linter configs)
• tests/** (test files)
• .gitignore, .editorconfig, etc.

User Feedback

When no important files are changed, a comment is automatically added to the PR explaining why build/test/publish stages will be skipped.

Rationale

This approach ensures that only meaningful changes to the module content result in new releases, avoiding version inflation from CI/CD maintenance or test-only changes.