-
Notifications
You must be signed in to change notification settings - Fork 2
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
Feature: create new release command #140
Labels
enhancement
New feature or request
Comments
theseion
added a commit
that referenced
this issue
Jan 1, 2025
- create and check out new version branch Fixes #140
Ok, forgot to add it to the issue, but maybe is too cumbersome to add a new git integration (unless we see the merit for additional things) just for this. I'm using this script for this now:
|
theseion
added a commit
that referenced
this issue
Jan 3, 2025
- create and check out new version branch Fixes #140
Added the missing stuff from your script to the PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With the idea of automating most of the process for releasing, these steps from the release procedure might be easily automated:
Requirements
Example command:
crs-toolchain release new -v v4.2.0
.This will:
release/$version
+release
post-release/$next-minor-version"-dev"
.+post-release
The text was updated successfully, but these errors were encountered: