Skip to content

Fix #240: Push only release tag #322

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 17, 2025
Merged

Fix #240: Push only release tag #322

merged 2 commits into from
Jun 17, 2025

Conversation

samdark
Copy link
Member

@samdark samdark commented Jun 15, 2025

Q A
Is bugfix? ✔️
New feature?
Breaks BC?
Fixed issues #240

@samdark samdark requested review from vjik, xepozz and Copilot June 15, 2025 19:30
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR fixes issue #240 by ensuring that only the release tag is pushed to GitHub instead of all tags.

  • Updates the release command to call pushTag() with the release version instead of pushing all tags.
Comments suppressed due to low confidence (1)

src/App/Command/Release/MakeCommand.php:187

  • Ensure that the pushTag() method is well-documented and verified to push only the intended release tag, as per the requirements of bug #240.
$git->pushTag((string) $versionToRelease);

Co-authored-by: Sergei Predvoditelev <sergei@predvoditelev.ru>
@samdark samdark merged commit 82c7d02 into master Jun 17, 2025
2 of 5 checks passed
@samdark samdark deleted the 240-push-only-release-tag branch June 17, 2025 21:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants