[GH-ISSUE #347] "git clone" cannot obtain AI contributions #123

New issue

Open

opened 2026-03-02 04:11:58 +03:00 by kerem · 1 comment

kerem commented

2026-03-02 04:11:58 +03:00

Owner

Originally created by @wangkaizhuang on GitHub (Jan 14, 2026).
Original GitHub issue: https://github.com/git-ai-project/git-ai/issues/347

Originally assigned to: @svarlamov, @Copilot on GitHub.

https://confluence.atlassian.com/bitbucketserver0717/personal-access-tokens-1087535496.html?utm_campaign=in-app-help&utm_medium=in-app-help&locale=zh_CN%2Czh&utm_source=stash#Personalaccesstokens-usingpersonalaccesstokens

The "clone" notation in the document

git clone https://username:MDM0MjM5NDc2MDxxxxxxxxxxxxxxxxxxxxx@bitbucketserver.com/scm/projectname/teamsinspace.git

After cloning, entering "git stats" and "show" in the code repository does not retrieve relevant information about AI notes and AI contribution. However, normal git cloning seems to support these commands. I'm not sure if you need to support this

Originally created by @wangkaizhuang on GitHub (Jan 14, 2026). Original GitHub issue: https://github.com/git-ai-project/git-ai/issues/347 Originally assigned to: @svarlamov, @Copilot on GitHub. https://confluence.atlassian.com/bitbucketserver0717/personal-access-tokens-1087535496.html?utm_campaign=in-app-help&utm_medium=in-app-help&locale=zh_CN%2Czh&utm_source=stash#Personalaccesstokens-usingpersonalaccesstokens The "clone" notation in the document git clone https://username:MDM0MjM5NDc2MDxxxxxxxxxxxxxxxxxxxxx@bitbucketserver.com/scm/projectname/teamsinspace.git After cloning, entering "git stats" and "show" in the code repository does not retrieve relevant information about AI notes and AI contribution. However, normal git cloning seems to support these commands. I'm not sure if you need to support this

kerem commented

2026-03-02 04:11:59 +03:00

Author

Owner

@svarlamov commented on GitHub (Feb 18, 2026):

@wangkaizhuang I believe this should be fixed now and if not yet certainly with the #530 (git hooks) this will be patched. Let me know if we can close this?

@svarlamov commented on GitHub (Feb 18, 2026): @wangkaizhuang I believe this should be fixed now and if not yet certainly with the #530 (git hooks) this will be patched. Let me know if we can close this?