gitea

Commit Graph

Author	SHA1	Message	Date
Giteabot	9903b8d7ec	Fix Bug in Issue Config when only contact links are set (#26521 ) (#27334 ) Backport #26521 by @JakobDev Blank Issues should be enabled if they are not explicit disabled through the `blank_issues_enabled` field of the Issue Config. The Implementation has currently a Bug: If you create a Issue Config file with only `contact_links` and without a `blank_issues_enabled` field, `blank_issues_enabled` is set to false by default. The fix is only one line, but I decided to also improve the tests to make sure there are no other problems with the Implementation. This is a bugfix, so it should be backported to 1.20. Co-authored-by: JakobDev <jakobdev@gmx.de>	1 year ago
wxiaoguang	def4956122	Improve Gitea's web context, decouple "issue template" code into service package (#24590 ) 1. Remove unused fields/methods in web context. 2. Make callers call target function directly instead of the light wrapper like "IsUserRepoReaderSpecific" 3. The "issue template" code shouldn't be put in the "modules/context" package, so move them to the service package. --------- Co-authored-by: Giteabot <teabot@gitea.io>	2 years ago

Author

SHA1

Message

Date

Giteabot

9903b8d7ec

Fix Bug in Issue Config when only contact links are set (#26521 ) (#27334 )

Backport #26521 by @JakobDev

Blank Issues should be enabled if they are not explicit disabled through
the `blank_issues_enabled` field of the Issue Config. The Implementation
has currently a Bug: If you create a Issue Config file with only
`contact_links` and without a `blank_issues_enabled` field,
`blank_issues_enabled` is set to false by default.

The fix is only one line, but I decided to also improve the tests to
make sure there are no other problems with the Implementation.

This is a bugfix, so it should be backported to 1.20.

Co-authored-by: JakobDev <jakobdev@gmx.de>

1 year ago

wxiaoguang

def4956122

Improve Gitea's web context, decouple "issue template" code into service package (#24590 )

1. Remove unused fields/methods in web context.
2. Make callers call target function directly instead of the light
wrapper like "IsUserRepoReaderSpecific"
3. The "issue template" code shouldn't be put in the "modules/context"
package, so move them to the service package.

---------

Co-authored-by: Giteabot <teabot@gitea.io>

2 years ago

2 Commits (b56a9f6dedd7c689ff22c8fdd34c5761bbae3fe2)