jdaugherty opened a new pull request, #132:
URL: https://github.com/apache/grails-forge-ui/pull/132
## Summary
The Publish workflow has been failing on `main` whenever a merge doesn't
change the built UI output (e.g. dependabot bumps to GitHub Actions versions in
#125 and #128). `publish.sh` runs with `set -e`, and `git commit` exits 1 on an
empty diff ("nothing to commit, working tree clean"), failing the whole run
even though the build succeeded.
The no-changes guard was previously commented out. This restores it, but
checks the **staged** diff after `git add -A` (`git diff --cached --quiet`) so
newly added files are also detected — the old pre-add `git diff --quiet` check
would have missed them.
## Testing
- `bash -n publish.sh` passes
- Behavior: identical build output → logs "No changes in Grails Forge UI"
and exits 0; changed output → commits and pushes to gh-pages as before
🤖 Generated with [Claude Code](https://claude.com/claude-code)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
