Fix Manual Release Tag Name in Workflow#12
Conversation
The previous commit allowed manual triggering of the release workflow but failed to set the `tag_name` in the `softprops/action-gh-release` step, causing the release creation to fail. This commit explicitly sets `tag_name` to `${{ inputs.tag || github.ref_name }}`, ensuring that manual releases are associated with the specified tag.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
Updated
.github/workflows/release.ymlto include thetag_nameparameter in theCreate Releasestep. This ensures that when the workflow is triggered manually with a tag input, the GitHub Release is correctly created with that tag, fixing the "GitHub Releases requires a tag" error.PR created automatically by Jules for task 8369023538800648245 started by @stevevanhooser