-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Add HOWTO for releasing Gitea #5054
Add HOWTO for releasing Gitea #5054
Conversation
Used instructions from: #2609 (comment)
CONTRIBUTING.md
Outdated
* After your PR reviewed and merged, and CI passed, add a tag as `git tag -s -F release.notes v$vmaj.$vmin.$`, release.notes file could be a temporory file to only include the changelog this version which you added to `CHANGELOG.md`. | ||
* And then push the tag as `git push origin v$vmaj.$vmin.$`. Drone CI will automatically created a release and upload all the compiled binary. (But currently it didn't add the release notes automatically. Maybe we should fix that.) | ||
* Send PR for changelog on branch `master`. | ||
* Send PR to https://github.com/go-gitea/blog announcing the release. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Send PR to https://github.com/go-gitea/blog announcing the release.
+ Send PR to [blog repository](https://github.com/go-gitea/blog) announcing the release.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for suggestion 😄. I've updated PR.
Codecov Report
@@ Coverage Diff @@
## master #5054 +/- ##
==========================================
+ Coverage 37.4% 37.42% +0.02%
==========================================
Files 306 306
Lines 45374 45374
==========================================
+ Hits 16970 16983 +13
+ Misses 25950 25941 -9
+ Partials 2454 2450 -4
Continue to review full report at Codecov.
|
Used instructions from: #2609 (comment)
These are the current steps, as discussed in other PR this process can be changed, however it is important to at least have the current process documented.