A Git platform powered by Scala with easy installation, high extensibility & github API compatibility
xuwei-k on master
Update postgresql to 42.2.18 C… (compare)
xuwei-k on master
Update mariadb-java-client to 2… (compare)
xuwei-k on master
Update oauth2-oidc-sdk to 8.34.2 (compare)
xuwei-k on master
Update ec4j-core to 0.0.4 (compare)
xuwei-k on master
Update cache2k-all to 1.6.0.Fin… (compare)
for example which page ?
Hmm, it's difficult to pick up some specific pages, because I updated nearly all pages in GitBucket.
Overall, I fixed below issues mainly.
https://web.dev/label/?utm_source=lighthouse&utm_medium=devtools
https://web.dev/link-name/?utm_source=lighthouse&utm_medium=devtools
https://web.dev/button-name/?utm_source=lighthouse&utm_medium=devtools
https://web.dev/duplicate-id-active/?utm_source=lighthouse&utm_medium=devtools
mydatabase
.* so the user definitely has permission
I think GitBucket has to call
ReceiveHook
even when pull request is merged so that you won't need to implementPRHook
aside fromCommitHook
. This is an issue on GitBucket side.
@takezoe, if you recall the GitBucket Git Hooks plugin I shared, you said that I shouldn't have to implement thePRHook
since GitBucket is supposed to call ReceiveHook
anyway. Do you know if this has already been fixed? We're currently on version 4.33.0
.