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
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.
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.
Description
Only publish if the important files have changes.
Discorvery