feat: one commit for release update#21
Conversation
There was a problem hiding this comment.
Pull request overview
This PR updates the release PR creation script to produce a single consolidated commit for release-related changes, instead of committing the version bump and changelog update separately.
Changes:
- Remove the separate
git commitcalls from the version bump and changelog sections. - Add a single “commit all staged release changes” step with a unified commit message.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| @@ -72,15 +72,18 @@ main() { | |||
| if [[ -f package-lock.json ]] && ! git diff --staged --quiet package-lock.json 2>/dev/null; then | |||
There was a problem hiding this comment.
The conditional that decides whether to git add package-lock.json is checking the staged diff (git diff --staged --quiet package-lock.json). At this point the lockfile hasn’t been staged yet, so this will typically report “no staged changes” and skip adding the lockfile even when npm version modified it. Use a working-tree/index check (e.g., git diff --quiet -- package-lock.json or git status --porcelain -- package-lock.json) so changed lockfiles are reliably included in the release commit.
| if [[ -f package-lock.json ]] && ! git diff --staged --quiet package-lock.json 2>/dev/null; then | |
| if [[ -f package-lock.json ]] && ! git diff --quiet -- package-lock.json 2>/dev/null; then |
No description provided.