-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Changelog for 1.21 missing CI approval notice #28570
Comments
Behaviour has changed as a result of this PR: Support for status check pattern (#24633) |
The feature introduced in #24633 should be compatible with gitea/routers/web/repo/pull.go Lines 653 to 663 in 21229ed
I'll try to make a PR to fix it |
Fix #28570 Follow #24633 --- Copied from #28570 (comment) The feature introduced in #24633 should be compatible with `status_check_contexts`. However, if one or more of `status_check_contexts` is not a legal glob expressions, `glob.Compile` will fail and the contexts cannot match. https://github.com/go-gitea/gitea/blob/21229ed2c8ed00f57100adf9ebc5f4a08da9a66e/routers/web/repo/pull.go#L653-L663
Fix go-gitea#28570 Follow go-gitea#24633 --- Copied from go-gitea#28570 (comment) The feature introduced in go-gitea#24633 should be compatible with `status_check_contexts`. However, if one or more of `status_check_contexts` is not a legal glob expressions, `glob.Compile` will fail and the contexts cannot match. https://github.com/go-gitea/gitea/blob/21229ed2c8ed00f57100adf9ebc5f4a08da9a66e/routers/web/repo/pull.go#L653-L663
Backport #28582 by @Zettat123 Fix #28570 Follow #24633 --- Copied from #28570 (comment) The feature introduced in #24633 should be compatible with `status_check_contexts`. However, if one or more of `status_check_contexts` is not a legal glob expressions, `glob.Compile` will fail and the contexts cannot match. https://github.com/go-gitea/gitea/blob/21229ed2c8ed00f57100adf9ebc5f4a08da9a66e/routers/web/repo/pull.go#L653-L663 Co-authored-by: Zettat123 <zettat123@gmail.com>
Fix go-gitea#28570 Follow go-gitea#24633 --- Copied from go-gitea#28570 (comment) The feature introduced in go-gitea#24633 should be compatible with `status_check_contexts`. However, if one or more of `status_check_contexts` is not a legal glob expressions, `glob.Compile` will fail and the contexts cannot match. https://github.com/go-gitea/gitea/blob/21229ed2c8ed00f57100adf9ebc5f4a08da9a66e/routers/web/repo/pull.go#L653-L663
Backport #28582 by @Zettat123 Fix #28570 Follow #24633 --- Copied from go-gitea/gitea#28570 (comment) The feature introduced in #24633 should be compatible with `status_check_contexts`. However, if one or more of `status_check_contexts` is not a legal glob expressions, `glob.Compile` will fail and the contexts cannot match. https://github.com/go-gitea/gitea/blob/21229ed2c8ed00f57100adf9ebc5f4a08da9a66e/routers/web/repo/pull.go#L653-L663 Co-authored-by: Zettat123 <zettat123@gmail.com> (cherry picked from commit 6a559ad)
Fix go-gitea#28570 Follow go-gitea#24633 --- Copied from go-gitea#28570 (comment) The feature introduced in go-gitea#24633 should be compatible with `status_check_contexts`. However, if one or more of `status_check_contexts` is not a legal glob expressions, `glob.Compile` will fail and the contexts cannot match. https://github.com/go-gitea/gitea/blob/21229ed2c8ed00f57100adf9ebc5f4a08da9a66e/routers/web/repo/pull.go#L653-L663
Fix go-gitea#28570 Follow go-gitea#24633 --- Copied from go-gitea#28570 (comment) The feature introduced in go-gitea#24633 should be compatible with `status_check_contexts`. However, if one or more of `status_check_contexts` is not a legal glob expressions, `glob.Compile` will fail and the contexts cannot match. https://github.com/go-gitea/gitea/blob/21229ed2c8ed00f57100adf9ebc5f4a08da9a66e/routers/web/repo/pull.go#L653-L663
Description
When upgrading from 1.20.5 to 1.21.2 the CI pipeline status checks were ignored in PRs.
I checked the release notes before updating the instance here, however nothing mentioned this change.
After investigating the database i found out, that when a repo had status checks enabled but no custom pattern was supplied it skipped the check.
When i updated the field
status_check_contexts
to[*]
status checks worked again.Query used to find "broken" branch status check entries:
Gitea Version
1.21.2
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
2.20.1
Operating System
Debian
How are you running Gitea?
Docker Compose
Image: gitea/gitea:1.21
Database
PostgreSQL
The text was updated successfully, but these errors were encountered: