-
-
Notifications
You must be signed in to change notification settings - Fork 6.2k
Fix different behavior in status check pattern matching with double stars #35474
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
Conversation
1fab533 to
d445b67
Compare
d445b67 to
3a663c4
Compare
* giteaofficial/main: Fix different behavior in status check pattern matching with double stars (go-gitea#35474) Replace webpack with rspack (go-gitea#35460) Don't store repo archives on `gitea dump` (go-gitea#35467) Fix SSH signing key path will be displayed in the pull request UI (go-gitea#35381) [skip ci] Updated translations via Crowdin Update image name in integration README (go-gitea#35465)
|
FYI: https://github.com/go-gitea/gitea/security/code-scanning/144, maybe a false-positive. It seems most of these code scanning results are bogus. |
False-positive. That code is only used for the special test data from Golang |
To fix: fd02f8b |
* origin/main: Clean up npm dependencies (go-gitea#35484) Update eslint to v9 (go-gitea#35485) Revert the rspack change (go-gitea#35482) Replace gobwas/glob package (go-gitea#35478) Fix various typos in codebase (go-gitea#35480) Fix different behavior in status check pattern matching with double stars (go-gitea#35474) Replace webpack with rspack (go-gitea#35460) Don't store repo archives on `gitea dump` (go-gitea#35467)
Drop the minimatch dependency, use our own glob compiler.
Fix #35473