Add dry-run flag to branch creation command#74
Open
jetm wants to merge 3 commits intoytreister:mainfrom
Open
Conversation
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Users currently cannot preview branch creation and push operations before they execute, making it risky to test branch name formats or verify behavior without actually modifying the repository state. This forces users to either test in throwaway repositories or manually undo unwanted operations. Add a --dry-run flag that logs intended Git operations without executing them. This allows users to safely verify branch names, confirm push behavior, and validate configurations before committing to repository changes. The implementation preserves all validation logic including dirty tree checks and existing branch conflicts, so dry-run output accurately reflects what would happen in a real run. Signed-off-by: Javier Tia <floss@jetm.me>
The project currently lacks integrated test coverage reporting capabilities. Developers must manually run coverage tools or rely on external CI configurations to assess code coverage during local development, making it difficult to verify that new code is adequately tested before committing. Add pytest-cov to a new dependency-groups.dev section in pyproject.toml to enable standardized coverage reporting during local development. This allows developers to run pytest with coverage flags using the same tooling configuration across all environments, ensuring consistent coverage metrics and simplifying the feedback loop for test completeness. Signed-off-by: Javier Tia <floss@jetm.me>
The current uv.lock file uses an older format that lacks package upload timestamp metadata. This information is valuable for security auditing, dependency verification, and detecting potentially compromised packages that may have been backdated or manipulated on package registries. Regenerate the lock file using the latest uv resolver which updates the format to revision 3. This adds upload-time fields to all package distribution entries while preserving existing package versions and hashes, ensuring reproducible builds with enhanced metadata. Signed-off-by: Javier Tia <floss@jetm.me>
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
2 participants
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.
Users currently cannot preview branch creation and push operations
before they execute, making it risky to test branch name formats or
verify behavior without actually modifying the repository state. This
forces users to either test in throwaway repositories or manually undo
unwanted operations.
Add a --dry-run flag that logs intended Git operations without
executing them. This allows users to safely verify branch names,
confirm push behavior, and validate configurations before committing
to repository changes. The implementation preserves all validation
logic including dirty tree checks and existing branch conflicts, so
dry-run output accurately reflects what would happen in a real run.
Address #39