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
*	Fix various documentation, user-facing, and source comment typos (#16367)	luzpaz	2021-07-08	1	-2/+2
\| \| \| \| \|	* Fix various doc, user-facing, and source comment typos Found via `codespell -q 3 -S ./options/locale,./vendor -L ba,pullrequest,pullrequests,readby`
*	chore(models): rewrite code format. (#14754)	Bo-Yi Wu	2021-03-14	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	* chore: rewrite format. * chore: update format Signed-off-by: Bo-Yi Wu <appleboy.tw@gmail.com> * chore: update format Signed-off-by: Bo-Yi Wu <appleboy.tw@gmail.com> * chore: Adjacent parameters with the same type should be grouped together * chore: update format.
*	Fix bug of migraition v111 (#12738)	Lunny Xiao	2020-09-06	1	-3/+3
\|
*	Fix bug on migration 111 (#12736)	Lunny Xiao	2020-09-06	1	-12/+32
\| \| \| \| \| \| \| \| \|	* Fix bug on migration 111 * Check reviews when migrating v111 * Fix bug * Fix commit
*	Fix bug preventing transfer to private organization (#12497)	zeripath	2020-08-16	1	-2/+2
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	* Fix bug preventing transfer to private organization The code assessing whether a private organization was visible to a user before allowing transfer was incorrect due to testing membership the wrong way round This PR fixes this issue and renames the function performing the test to be clearer. Further looking at the API for transfer repository - no testing was performed to ensure that the acting user could actually see the new owning organization. Signed-off-by: Andrew Thornton <art27@cantab.net> * change IsUserPartOfOrg everywhere
*	Refactor: Remove Dependencies from Migration v111 (#11646)	6543	2020-07-26	1	-15/+344
\| \| \| \| \| \| \|	* Refactor: Remove Dependencys from Migration v111 * Update models/migrations/v111.go Co-authored-by: techknowlogick <techknowlogick@gitea.io>
*	Issue with Migration rule v111 (#9449)	Marge Bouvier	2019-12-21	1	-0/+3
\| \| \| \| \| \| \| \| \| \| \| \|	* Issue with Migration rule v111 I was facing some issues with migration rule v111 * Update v111.go Fix pgsql test cases Co-authored-by: Antoine GIRARD <sapk@users.noreply.github.com>
*	Branch protection: Possibility to not use whitelist but allow anyone with ↵	David Svantesson	2019-12-03	1	-0/+87
	write access (#9055) * Possibility to not use whitelist but allow anyone with write access * fix existing test * rename migration function * Try to give a better name for migration step * Clear settings if higher level setting is not set * Move official reviews to db instead of counting approvals each time * migration * fix * fix migration * fix migration * Remove NOT NULL from EnableWhitelist as migration isn't possible * Fix migration, reviews are connected to issues. * Fix SQL query issues in GetReviewersByPullID. * Simplify function GetReviewersByIssueID * Handle reviewers that has been deleted * Ensure reviews for test is in a well defined order * Only clear and set official reviews when it is an approve or reject.