We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Once we have created a weekly build process in #334 we should update the system that automatically tags releases
The new release tag should be identified by searching for highest commit tag with the format:
/alpha-(?P<major>[0-9]+)\.(?P<minor>[0-9]+)\.(?P<revision>[0-9]+)/
and then setting the release tag to be alpha-{major}.{minor+1}.0
alpha-{major}.{minor+1}.0
After #333 is completed we will change this logic to be
/release-(?P<major>[0-9]+)\.(?P<minor>[0-9]+)\.(?P<revision>[0-9]+)/
and the tag will be release-{major}.{minor+1}.0 so the words alpha and release should be an easily editable variable if possible.
release-{major}.{minor+1}.0
alpha
release
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Once we have created a weekly build process in #334 we should update the system that automatically tags releases
The new release tag should be identified by searching for highest commit tag with the format:
and then setting the release tag to be
alpha-{major}.{minor+1}.0
After #333 is completed we will change this logic to be
and the tag will be
release-{major}.{minor+1}.0
so the words
alpha
andrelease
should be an easily editable variable if possible.The text was updated successfully, but these errors were encountered: