gitea

Commit Graph

Author	SHA1	Message	Date
Lunny Xiao	e5a8ebc0ed	Require at least one unit to be enabled (#24189 ) Don't remember why the previous decision that `Code` and `Release` are non-disable units globally. Since now every unit include `Code` could be disabled, maybe we should have a new rule that the repo should have at least one unit. So any unit could be disabled. Fixes #20960 Fixes #7525 --------- Co-authored-by: delvh <dev.lh@web.de> Co-authored-by: yp05327 <576951401@qq.com>	2023-05-06 17:39:06 +07:00
Jason Song	d67e40684f	Improve LoadUnitConfig to handle invalid or duplicate units (#23736 ) The old code just parses an invalid key to `TypeInvalid` and uses it as normal, and duplicate keys will be kept. So this PR will ignore invalid key and log warning and also deduplicate valid units.	2023-04-03 16:42:38 +07:00

Author

SHA1

Message

Date

Lunny Xiao

e5a8ebc0ed

Require at least one unit to be enabled (#24189 )

Don't remember why the previous decision that `Code` and `Release` are
non-disable units globally. Since now every unit include `Code` could be
disabled, maybe we should have a new rule that the repo should have at
least one unit. So any unit could be disabled.

Fixes #20960
Fixes #7525

---------

Co-authored-by: delvh <dev.lh@web.de>
Co-authored-by: yp05327 <576951401@qq.com>

2023-05-06 17:39:06 +07:00

Jason Song

d67e40684f

Improve LoadUnitConfig to handle invalid or duplicate units (#23736 )

The old code just parses an invalid key to `TypeInvalid` and uses it as
normal, and duplicate keys will be kept.

So this PR will ignore invalid key and log warning and also deduplicate
valid units.

2023-04-03 16:42:38 +07:00

2 Commits (77bd3acb65f88891af3a57e2521ce91108bd2f5c)