🚀[Feature]: Allow users to configure important release-triggering files via settings file and action.yml defaults #278
Description
Feature Request: Configurable Release File List with Explicit Defaults
Currently, the criteria for which files are considered "important" and trigger a new release are hardcoded into the GitHub Action/workflow. This limits flexibility and requires code changes each time a new file should warrant a release.
Proposed Enhancement
- Add support for specifying important files (those that, when changed, should trigger a new release) as parameters/inputs/config items in the settings file.
- Allow users to override the default list of release-triggering files through configuration, instead of modifying workflow logic directly.
- The default value should be moved to the action.yml file, and specified as the default for the relevant input. The input overview and documentation should state what the defaults are. The input should not default to blank and revert to current hardcoded logic; instead, defaults must be specified and visible in action.yml.
- The release workflow should dynamically reference this configurable list for its trigger logic.
Acceptance Criteria
- The settings file (or equivalent config) should accept a list of file paths/patterns designated as important.
- action.yml must specify explicit defaults for the input, reflected in both the file and the input overview documentation.
- The release workflow must use the input default from action.yml if not overridden by user config.
- Defaults should remain for backward compatibility, but user override takes precedence.
- Documentation must be updated to reflect this new behavior.
Motivations
- Provides greater flexibility to users managing releases in the repo.
- Reduces workflow maintenance overhead.
- Accommodates repo-specific needs as they change over time.
- Makes defaults transparent and easier to discover/manage.