Skip to content
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

gitee: When the name and path are inconsistent, got 404 error #217

Closed
KeJunMao opened this issue Aug 17, 2022 · 4 comments
Closed

gitee: When the name and path are inconsistent, got 404 error #217

KeJunMao opened this issue Aug 17, 2022 · 4 comments

Comments

@KeJunMao
Copy link

like this:

the repo name is Storyline 360 User Guide

but the repo paht is Storyline-360-User-Guide

ch07_2022-08-18 00 48 21

in drone repo list:
ch07_2022-08-18 00 51 30

in drone repo detail:
ch07_2022-08-18 00 51 38

@ShruthiHubb
Copy link

Hi @KeJunMao can you give us more context here to troubleshoot this issue?

Thanks
Shruthi Kini

@KeJunMao
Copy link
Author

KeJunMao commented Sep 14, 2022

Hi @ShruthiHubb

check here
harness/gitness#3250 (comment)

or use curl

curl -X GET --header 'Content-Type: application/json;charset=UTF-8' 'https://gitee.com/api/v5/users/Ke_Jun/repos?type=all&sort=full_name&page=1&per_page=20'

check response root[3]

...
"id": 1039816
"full_name": "Ke_Jun/Storyline-2-User-Guide-zh_cn"
"human_name": "Ke_Jun/Storyline 2 User Guide-zh_cn"
"url": "https://gitee.com/api/v5/repos/Ke_Jun/Storyline-2-User-Guide-zh_cn"
"path": "Storyline-2-User-Guide-zh_cn"
"name": "Storyline 2 User Guide-zh_cn"
"description": "storyline2用户指南-简体中文"
...

the human_name include space, but drone should use full_name as slug

or , name include space, slug should use path?

@bradrydzewski
Copy link
Member

bradrydzewski commented Sep 16, 2022

I cannot comment on Gitee since I do not have any experience, but Bitbucket has similar options, and for Bitbucket we use the full_name equivalent. I suspect we should use full_name for Gitee too. Since Gitee is a community contribution and is community supported, we would kindly ask that a member of the community test the proposed fix and submit a patch. Thanks!

@bradrydzewski
Copy link
Member

fixed by #226

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants