@@ -43,9 +43,9 @@ Based on conventional commits since the last tag, determine the version bump:
4343
4444Show:
4545- Current version
46- - Commits since last tag (grouped by type)
46+ - Commits since the last tag (grouped by type)
4747- Suggested new version with reasoning
48- - Ask user to confirm or specify a different version
48+ - Ask the user to confirm or specify a different version
4949
5050Example:
5151```
@@ -65,7 +65,7 @@ Options:
6565
6666### 4. Create Tag Summary
6767
68- Ask the user for a concise summary description, or suggest one based on the commits.
68+ Ask the user for a concise summary description or suggest one based on the commits.
6969
7070The tag message format follows this pattern:
7171```
@@ -116,20 +116,20 @@ Then show:
116116
117117- Always get user confirmation before creating and pushing tags
118118- NEVER push tags without explicit confirmation
119- - If no commits since last tag, inform user and stop
119+ - If no commits since the last tag, inform the user and stop
120120- Validate version format (must be semantic versioning: X.Y.Z)
121- - Check if tag already exists before creating
122- - If push fails, show error and suggest solutions
121+ - Check if the tag already exists before creating
122+ - If the push fails, show error and suggest solutions
123123
124124## Error Handling
125125
126- If tag already exists:
126+ If the tag already exists:
127127- Show error message
128- - Ask if user wants to delete and recreate (not recommended)
129- - Suggest incrementing version instead
128+ - Ask if the user wants to delete and recreate (not recommended)
129+ - Suggest an incrementing version instead
130130
131- If push fails:
131+ If the push fails:
132132- Check internet connection
133133- Verify git remote is configured
134- - Show full error message
135- - Suggest running ` git remote -v ` to check remote configuration
134+ - Show the full error message
135+ - Suggest running ` git remote -v ` to check remote configuration
0 commit comments