Naoki Takezoe

Then, that would be a LDAP configuration issue. Is that a different one from one which is originally reported by this issue? If so, could you show the error log...

I see, that means some changes in GitBucket affected. Actually, I don't have much experience with LDAP, and LDAP related changes in GitBucket in the history are very few: https://github.com/gitbucket/gitbucket/commits/master/src/main/scala/gitbucket/core/util/LDAPUtil.scala...

See also https://github.com/gitbucket/gitbucket/issues/2718

I meant that just changing the message doesn't work because GitBucket uses `master` as the default branch. And we haven't yet reached to get agreement on changing the default branch...

> When a token is set-up for an account, it can be used as a password @Sherpard Do you mean using a token as a password to access Git repository?

I see. Thanks for clarification. I plan to fix it in the next release.

You reported that `object.url` in response is: ``` https://GITBUCKET.FQDN/api/v3/repos/ORG_NAME/REPO_NAME/git/tags/2c950780ca32951f705889455afcd81f5b2de3c7 ``` but it actually should be: ``` https://GITBUCKET.FQDN/api/v3/repos/ORG_NAME/REPO_NAME/commits/2c950780ca32951f705889455afcd81f5b2de3c7 ``` https://github.com/gitbucket/gitbucket/blob/56df833b4aa8bf1b0101b67fee8236c99c3d1f0a/src/main/scala/gitbucket/core/api/ApiRef.scala#L51 and this url returns commit info properly.

> For example try to create a rethinkdb repo with this url https://github.com/rethinkdb/rethinkdb on the 4.21.2 demo install . Specify a git repository url instead as: https://github.com/rethinkdb/rethinkdb.git

Hmm, I cannot reproduce the case. Could you provide more info?

Thanks for investigation. Sounds like we can optimize it. I think we can deal with it in 4.36.0.