Skip to content
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

Revision option for prepare #34

Closed
Jean85 opened this issue Dec 19, 2019 · 4 comments · Fixed by #223
Closed

Revision option for prepare #34

Jean85 opened this issue Dec 19, 2019 · 4 comments · Fixed by #223
Labels
enhancement New feature or request

Comments

@Jean85
Copy link

Jean85 commented Dec 19, 2019

Hi! It would be nice to add the --rev option for the prepare command, is it possible?

@tonyo
Copy link
Contributor

tonyo commented Dec 19, 2019

What would be the semantics of prepare with rev provided?
Do you want to create the release branch based on that revision?

@tonyo tonyo added the question Further information is requested label Dec 19, 2019
@Jean85
Copy link
Author

Jean85 commented Dec 19, 2019

Yes, exactly. I needed that today here: getsentry/sentry-symfony#283
Master was already ahead (3.3.x, new minor version) and I needed to release a patch (3.2.1) using
8a176d7 as a revision, before merging master in that branch.

craft release --rev is able to do that, but I do not have enough permission, so @HazAT had to do that for me, without my help and review beforehand with craft prepare.

@Jean85 Jean85 changed the title Reviosion option for prepare Revision option for prepare Dec 19, 2019
@tonyo
Copy link
Contributor

tonyo commented Dec 20, 2019

Just to clarify: as far as I understand, the agreement here was that release would be run by @HazAT anyway, so adding new features to prepare will not really fix it.

Regarding the feature itself, generally I agree that it'd make sense to add it.
To agree on the semantics, craft prepare --rev REV VERSION will do the following:

  • Checkout REV
  • Check that the changelog for the new version (VERSION) is there (if the changelog check is configured)
  • Create a new release branch
  • Run pre-release command (which is user-configured, it usually bumps the version in some files, and you can run some additional checks there) and commit the changes
  • Push the release branch

Does it sound good?

@Jean85
Copy link
Author

Jean85 commented Dec 20, 2019

Yes, absolutely!

@tonyo tonyo added enhancement New feature or request and removed question Further information is requested labels Feb 10, 2020
BYK added a commit that referenced this issue May 10, 2021
BYK added a commit that referenced this issue May 10, 2021
BYK added a commit that referenced this issue May 10, 2021
BYK added a commit that referenced this issue May 10, 2021
@BYK BYK closed this as completed in #223 May 11, 2021
BYK added a commit that referenced this issue May 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants