ci: add GitHub Actions workflow for automated release pull requests #115
Conversation
| workflow_dispatch: | ||
| inputs: | ||
| scope: | ||
| description: "Package name to release (e.g., altfire_authenticator)" | ||
| required: true |
There was a problem hiding this comment.
I think this should be a selection rather than free input!
It looks like type: choice could be useful here ✍️
There was a problem hiding this comment.
There are cases where multiple packages are updated simultaneously like this, so making it optional might be a good idea 💭
| env: | ||
| MELOS_ALLOW_DIRTY: "true" | ||
| run: | | ||
| melos version --patch --no-private --yes --scope="${{ github.event.inputs.scope }}" |
There was a problem hiding this comment.
I was thinking it might be better not to make the patch version change fixed. What do you think?
It might be better to remove --patch and let it be determined automatically!
There was a problem hiding this comment.
Since melos version can determine the version increment automatically, specifying --patch is unnecessary.
I’ll remove it.🙏🏻
| id: set-output | ||
| run: | | ||
| BRANCH_NAME="release/${{ github.event.inputs.scope }}-${{ env.version }}" | ||
| echo "branch=$BRANCH_NAME" >> "$GITHUB_ENV" |
There was a problem hiding this comment.
My understanding is that GITHUB_ENV is meant to be used across different steps within the same job, so it seems unnecessary here!
🔗 Issue Link
related: #78
🙌 What I did
✍️ What I didn't do
✅ Verification
Screenshots
Additional Information
First, I created a workflow that automatically generates a pull request using the Melos version.
Separately, I will create another workflow to automatically publish to pub.dev.