-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
add make version on gitea version #6485
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
Conversation
Codecov Report
@@ Coverage Diff @@
## master #6485 +/- ##
=========================================
Coverage ? 40.18%
=========================================
Files ? 402
Lines ? 54021
Branches ? 0
=========================================
Hits ? 21706
Misses ? 29307
Partials ? 3008 Continue to review full report at Codecov.
|
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.
It's a shame we can't get to
Go build to update the version too.
Seems like clutter to me This reverts commit 0a8e63c.
…o-gitea#6645) Closes go-gitea#6485 Adds a bit of javascript in the template responsible for the "create release" page When typing a name in the "tag name" field, the content will be automatically set in the "Title" field as a placeholder. This way, you can type a version number (ex: `v5.0.2`), and the title will default to it (`v5.0.2` in this case) ## Checklist The [contributor guide](https://forgejo.org/docs/next/contributor/) contains information that will be helpful to first time contributors. There also are a few [conditions for merging Pull Requests in Forgejo repositories](https://codeberg.org/forgejo/governance/src/branch/main/PullRequestsAgreement.md). You are also welcome to join the [Forgejo development chatroom](https://matrix.to/#/#forgejo-development:matrix.org). ### Tests - I added test coverage for Go changes... - [ ] in their respective `*_test.go` for unit tests. - [ ] in the `tests/integration` directory if it involves interactions with a live Forgejo server. - I added test coverage for JavaScript changes... - [ ] in `web_src/js/*.test.js` if it can be unit tested. - [x] in `tests/e2e/*.test.e2e.js` if it requires interactions with a live Forgejo server (see also the [developer guide for JavaScript testing](https://codeberg.org/forgejo/forgejo/src/branch/forgejo/tests/e2e/README.md#end-to-end-tests)). ### Documentation - [ ] I created a pull request [to the documentation](https://codeberg.org/forgejo/docs) to explain to Forgejo users how to use this change. - [x] I did not document these changes and I do not expect someone else to do it. ### Release notes - [x] I do not want this change to show in the release notes. - [ ] I want the title to show in the release notes with a link to this pull request. - [ ] I want the content of the `release-notes/<pull request number>.md` to be be used for the release notes instead of the title. Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/6645 Reviewed-by: Gusted <[email protected]> Co-authored-by: Litchi Pi <[email protected]> Co-committed-by: Litchi Pi <[email protected]>
As title. When build with

go build
,When build with

make build
,