gitea.git - Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD: https://github.com/go-gitea/gitea

	Commit message (Collapse)	Author	Age	Files	Lines
*	Split migrations folder (#21549)	Lunny Xiao	2022-11-02	1	-0/+20
\| \| \| \|	There are too many files in `models/migrations` folder so that I split them into sub folders.
*	Allow creation of OAuth2 applications for orgs (#18084)	qwerty287	2022-10-09	1	-0/+10
\| \| \| \| \| \| \| \| \| \|	Adds the settings pages to create OAuth2 apps also to the org settings and allows to create apps for orgs. Refactoring: the oauth2 related templates are shared for instance-wide/org/user, and the backend code uses `OAuth2CommonHandlers` to share code for instance-wide/org/user. Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
*	Add new CSS variables --color-accent and --color-small-accent (#21305)	delvh	2022-10-07	1	-4/+4
\| \| \| \| \| \| \| \|	At the moment, this is only used to replace the color of the `viewed` checkbox and of the `has changed` label. Previously, the used variable accentuated always either darker or lighter, which meant that one theme looked good while the other didn't. Co-authored-by: silverwind <me@silverwind.io>
*	Prevent invalid behavior for file reviewing when loading more files (#21230)	delvh	2022-09-22	1	-0/+5
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	The problem was that many PR review components loaded by `Show more` received the same ID as previous batches, which confuses browsers (when clicked). All such occurrences should now be fixed. Additionally improved the background of the `viewed` checkbox. Lastly, the `go-licenses.json` was automatically updated. Fixes #21228. Fixes #20681. Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
*	Generate go-licenses during tidy again (#21108)	silverwind	2022-09-09	1	-5/+0
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	We can not have the `frontend` target depend on golang because of they way drone is set up. Move the `go-licenses` generation back into `tidy` where it will now also be checked for consistency during `tidy-check`. (I assume all `main` branch builds should currently fail [like this](https://drone.gitea.io/go-gitea/gitea/60244/1/11)). The reasony why it shouldn't be treated the same as for example `go generate` is because output files are checked in. tidy is imho the optimal target to run this after. Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
*	Rewrite go license generator in go (#21078)	silverwind	2022-09-07	1	-214/+364
\| \| \| \| \| \| \| \| \| \|	This removes the JS dependency in the checks pipeline. JSON output is different because the previous JS did indent the license data differently and a JSON key was changed, but the end result is the same as it gets re-indented by wepack. Co-authored-by: 6543 <6543@obermui.de> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> Co-authored-by: zeripath <art27@cantab.net>
*	Add go licenses to licenses.txt (#21034)	silverwind	2022-09-04	1	-0/+762
	`make go-licenses` will generate `assets/go-licenses.json` which is then included in the webpack build. This step depends on both go and node being present, so unfortunately, I could not automate the generation by hooking it up to `tidy` as that target is triggered on CI where we do not have a docker image with both go an node. It should be ran from time to time, ideally after each go mod update.