Create scheduled release PR workflow - #1044
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| - name: Commit version bump | ||
| if: steps.release_changes.outputs.proceed == 'true' | ||
| run: | | ||
| git add apps/client/package.json | ||
| git commit -m "chore: release v${{ steps.version.outputs.next_version }}" |
There was a problem hiding this comment.
Avoid pre-committing version bump before create-pull-request
When changes are detected, the workflow commits the bumped apps/client/package.json itself (git commit in the preceding step) and then calls peter-evans/create-pull-request. That action only opens a PR when there are uncommitted workspace changes; if the working tree is already clean it logs “no changes” and exits without creating or updating a PR. Because the version bump is pre-committed, every run will hit the clean-tree path and the scheduled release PR will never be opened despite the version change. Let the action create the commit instead of doing it manually.
Useful? React with 👍 / 👎.
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: karlorz <142769090+karlorz@users.noreply.github.com>
Summary
Testing
Codex Task