-
-
Notifications
You must be signed in to change notification settings - Fork 247
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
Automate release tagging in Git #5863
Comments
/bounty 80 |
💎 $80 bounty • Mudlet🔨 See instructions for compiling Mudlet Steps to solve:
Thank you for contributing to Mudlet/Mudlet! Add a bounty • Share on socials
|
/attempt #5863
|
💡 @ibishal submitted a pull request that claims the bounty. You can visit your bounty board to reward. |
@vadi2 can you explain a bit about this issue? |
💡 @pi600 submitted a pull request that claims the bounty. You can visit your bounty board to reward. |
💡 @guptadeepak8 submitted a pull request that claims the bounty. You can visit your bounty board to reward. |
We're putting this bounty on hold while we work out a better plan for release automation. |
@vadi2 when you reopen the bounty a tag will be appreciated |
Brief summary of issue / Description of requested feature:
Need to automate this step:
Edit: this should automatically happen off a new Github release (example). The release tag would the the new version that needs to go into mudlet.pro and CMakeLists.txt, and that is what Mudlet binaries need to be built with.
Steps to reproduce the issue / Reasons for adding feature:
The text was updated successfully, but these errors were encountered: