@@ -29,14 +29,14 @@ jobs:
2929 else
3030 TARGET_INFO="- **Target Commit:** Latest commit on current branch (HEAD)"
3131 fi
32-
32+
3333 cat >> $GITHUB_STEP_SUMMARY << EOF
3434 # 🚀 Create Release Workflow
35-
35+
3636 ## ℹ️ Workflow Information
3737 - **Version:** ${{ github.event.inputs.version }}
3838 $TARGET_INFO
39-
39+
4040 EOF
4141
4242 - name : Validate commit SHA (if provided)
@@ -46,14 +46,14 @@ jobs:
4646 if ! git rev-parse --verify "$COMMIT_SHA^{commit}" >/dev/null 2>&1; then
4747 cat >> $GITHUB_STEP_SUMMARY << EOF
4848 ## ❌ Error: Invalid Commit SHA
49-
49+
5050 The provided commit SHA \`$COMMIT_SHA\` is not valid or does not exist in this repository.
51-
51+
5252 ### 📝 Troubleshooting
5353 - Verify the commit SHA exists in the repository
5454 - Ensure you are using the full commit SHA (or at least 7 characters)
5555 - Check that the commit is in the current branch history
56-
56+
5757 EOF
5858 echo "Error: Invalid commit SHA: $COMMIT_SHA"
5959 exit 1
@@ -92,23 +92,23 @@ jobs:
9292 if [ ! -f "$CHANGELOG_FILE" ]; then
9393 cat >> $GITHUB_STEP_SUMMARY << EOF
9494 ## ❌ Error: Release Notes File Not Found
95-
95+
9696 The release notes file was not found at the expected location:
97-
97+
9898 \`\`\`
9999 $CHANGELOG_FILE
100100 \`\`\`
101-
101+
102102 ### 📝 What to do:
103103 1. Ensure you have created the changelog file for version \`${{ steps.set_vars.outputs.tag_name }}\`
104104 2. The file should be located at: \`.changes/${{ steps.set_vars.outputs.tag_name }}.md\`
105105 3. You can use \`changie batch <version>\` to generate the changelog file
106-
106+
107107 ### 📂 Available changelog files:
108108 \`\`\`
109109 $(ls -1 .changes/*.md 2>/dev/null || echo "No changelog files found")
110110 \`\`\`
111-
111+
112112 EOF
113113 echo "Error: Release notes file not found at $CHANGELOG_FILE"
114114 exit 1
@@ -121,14 +121,14 @@ jobs:
121121 run : |
122122 cat >> $GITHUB_STEP_SUMMARY << EOF
123123 ## 🏗️ Creating Release
124-
124+
125125 Creating release with the following details:
126126 - **Tag:** \`${{ steps.set_vars.outputs.tag_name }}\`
127127 - **Target Commit:** \`${{ steps.set_vars.outputs.actual_sha }}\`
128128 - **Notes File:** \`${{ steps.set_vars.outputs.changelog_file_path }}\`
129-
129+
130130 EOF
131-
131+
132132 # Create the release with the target commit
133133 if gh release create ${{ steps.set_vars.outputs.tag_name }} \
134134 --title "${{ steps.set_vars.outputs.tag_name }}" \
@@ -137,32 +137,32 @@ jobs:
137137
138138 cat >> $GITHUB_STEP_SUMMARY << EOF
139139 ## ✅ Release Created Successfully!
140-
140+
141141 🎉 **Release \`${{ steps.set_vars.outputs.tag_name }}\` has been created!**
142-
142+
143143 ### 📋 Release Details:
144144 - **Tag:** \`${{ steps.set_vars.outputs.tag_name }}\`
145145 - **Commit:** \`${{ steps.set_vars.outputs.actual_sha }}\`
146146 - **Release URL:** [View Release](https://github.com/${{ github.repository }}/releases/tag/${{ steps.set_vars.outputs.tag_name }})
147-
147+
148148 EOF
149149 else
150150 cat >> $GITHUB_STEP_SUMMARY << EOF
151151 ## ❌ Error: Failed to Create Release
152-
152+
153153 The GitHub CLI failed to create the release. This could be due to:
154-
154+
155155 ### 🔍 Common Issues:
156156 - A release with tag \`${{ steps.set_vars.outputs.tag_name }}\` already exists
157157 - Insufficient permissions to create releases
158158 - Network connectivity issues
159159 - Invalid release notes format
160-
160+
161161 ### 📝 Next Steps:
162162 1. Check if the tag already exists: \`git tag -l '${{ steps.set_vars.outputs.tag_name }}'\`
163163 2. Verify you have the necessary permissions to create releases
164164 3. Review the workflow run logs for detailed error messages
165-
165+
166166 EOF
167167 echo "Error: Failed to create release"
168168 exit 1
0 commit comments