Skip to content

API call (commits/{ref}/statuses) dont work #7784

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

Closed
2 of 7 tasks
DjSni opened this issue Aug 7, 2019 · 3 comments · Fixed by #7785
Closed
2 of 7 tasks

API call (commits/{ref}/statuses) dont work #7784

DjSni opened this issue Aug 7, 2019 · 3 comments · Fixed by #7785
Labels

Comments

@DjSni
Copy link

DjSni commented Aug 7, 2019

  • Gitea version (or commit ref): 1.9.0 Stable
  • Git version: 2.17.1
  • Operating system: Ubuntu 18.04.2 LTS (GNU/Linux 4.18.0-21-generic x86_64)
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

curl -X GET "https://try.gitea.io/api/v1/repos/gitea/gitea/commits/master/statuses" -H "accept: application/json"

Description

if i make an API call with "/repos/{owner}/{repo}/commits/{ref}/statuses" i get only an empty output back.

Screenshots

Screenshot_107
Screenshot_106
Screenshot_105

@sapk
Copy link
Member

sapk commented Aug 7, 2019

status are details attached by CI this is similar to Github API https://developer.github.com/v3/repos/statuses/. In the case of try.gitea.io, there is no CI configurated on this instance so no statuses.

@sapk
Copy link
Member

sapk commented Aug 7, 2019

@sapk
Copy link
Member

sapk commented Aug 7, 2019

@lunny lunny added the type/bug label Aug 8, 2019
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants