Repository navigation
docs: improve release process documentation with explicit git commands - #79
Merged
Merged
Conversation
- Add explicit git commit and tag creation step - Add explicit git push commands - Clarify CI automation trigger - Add direct link to GitHub releases page 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request
Description
This PR improves the release process documentation in the README by adding explicit git commands and clarifying the automation steps. The changes make it easier for maintainers to follow the release workflow by providing clear, actionable commands at each step.
Type of Change
Changes Made
Testing
Additional Notes
The updated documentation now provides a clearer separation between what maintainers need to do manually (steps 1-4, 6) and what GitHub Actions handles automatically (step 5). This should reduce confusion during the release process and ensure all necessary git operations are performed correctly.