[Meta] Improvements to the API #29

@bkcsoft commented on GitHub (Nov 4, 2016):

@tboerger Should this be a "Project" instead maybe?

@bkcsoft commented on GitHub (Nov 4, 2016): @tboerger Should this be a "Project" instead maybe?

GiteaMirror commented

@hhenkel commented on GitHub (Nov 4, 2016):

One point I already mentioned on the gitter channel yesterday, IMHO there is a need for automatic documentation (from code / comments in the code) of the api. I think this should be added to this list, there is an initial issue in go-gogs-client mentioning one of the current issues with the docs: https://github.com/gogits/go-gogs-client/issues/46

It seems swagger is the most popular solution currently and it seems there is a go implementation

@hhenkel commented on GitHub (Nov 4, 2016): One point I already mentioned on the gitter channel yesterday, IMHO there is a need for automatic documentation (from code / comments in the code) of the api. I think this should be added to this list, there is an initial issue in go-gogs-client mentioning one of the current issues with the docs: https://github.com/gogits/go-gogs-client/issues/46 It seems [swagger](http://swagger.io/) is the most popular solution currently and it seems there is a [go implementation](https://goswagger.io/)

GiteaMirror commented

@metalmatze commented on GitHub (Nov 4, 2016):

Yep 👍 for swagger

@metalmatze commented on GitHub (Nov 4, 2016): Yep :+1: for swagger

GiteaMirror commented

@tboerger commented on GitHub (Nov 4, 2016):

Maybe a project should be better to keep an overview of missing parts.

@tboerger commented on GitHub (Nov 4, 2016): Maybe a project should be better to keep an overview of missing parts.

GiteaMirror commented

@bkcsoft commented on GitHub (Nov 4, 2016):

@tboerger AFAIK it's hard to make generic comments (like @hhenkel just did) on a Project?

@bkcsoft commented on GitHub (Nov 4, 2016): @tboerger AFAIK it's hard to make generic comments (like @hhenkel just did) on a Project?

GiteaMirror commented

@tboerger commented on GitHub (Nov 4, 2016):

We should create issues for all of that.

@tboerger commented on GitHub (Nov 4, 2016): We should create issues for all of that.

GiteaMirror commented

@lunny commented on GitHub (Nov 9, 2016):

I think this should be the emphasis of v1.1. So we have to list all the APIs should github have. And implements it one by one. For example, we can implement https://developer.github.com/v3/repos/statuses first?

@lunny commented on GitHub (Nov 9, 2016): I think this should be the emphasis of v1.1. So we have to list all the APIs should github have. And implements it one by one. For example, we can implement https://developer.github.com/v3/repos/statuses first?

GiteaMirror commented

@bkcsoft commented on GitHub (Nov 10, 2016):

@lunny I have a few PRs coming, but I'll continue with the rest of the API after that starting with Status API :)

@bkcsoft commented on GitHub (Nov 10, 2016): @lunny I have a few PRs coming, but I'll continue with the rest of the API after that starting with `Status API` :)

GiteaMirror commented

@lunny commented on GitHub (Nov 10, 2016):

+1

@lunny commented on GitHub (Nov 10, 2016): +1

GiteaMirror commented

@pyhedgehog commented on GitHub (Dec 20, 2016):

Please add API for POST /api/v1/repos/:owner/:repo/forks. It's very important feature.

@pyhedgehog commented on GitHub (Dec 20, 2016): Please add API for [POST /api/v1/repos/:owner/:repo/forks](https://developer.github.com/v3/repos/forks/#create-a-fork). It's very important feature.

GiteaMirror commented

@bkcsoft commented on GitHub (Dec 25, 2016):

@pyhedgehog Please make an issue for that, since this is just a Meta-issue for tracking API-changes 🙂

@bkcsoft commented on GitHub (Dec 25, 2016): @pyhedgehog Please make an issue for that, since this is just a Meta-issue for tracking API-changes 🙂

GiteaMirror commented

@pyhedgehog commented on GitHub (Dec 25, 2016):

@bkcsoft, #477 + #494.

@pyhedgehog commented on GitHub (Dec 25, 2016): @bkcsoft, #477 + #494.

GiteaMirror commented

@bkcsoft commented on GitHub (Jan 29, 2017):

@lunny

and don't set a milestone either since it's long-running

:trollface:

@bkcsoft commented on GitHub (Jan 29, 2017): @lunny > and don't set a milestone either since it's long-running :trollface:

GiteaMirror commented

@lunny commented on GitHub (Jan 30, 2017):

OK

@lunny commented on GitHub (Jan 30, 2017): OK

GiteaMirror commented

@tboerger commented on GitHub (Feb 10, 2017):

But since it will be done within the 1.x.x livetime I will set it to 1.x.x milestone :trollface:

@tboerger commented on GitHub (Feb 10, 2017): But since it will be done within the 1.x.x livetime I will set it to 1.x.x milestone :trollface:

GiteaMirror commented

@bkcsoft commented on GitHub (Feb 12, 2017):

:trollface: (GitHub needs more reactions! )

@bkcsoft commented on GitHub (Feb 12, 2017): :trollface: (GitHub needs more reactions! )

GiteaMirror commented

@lunny commented on GitHub (Dec 31, 2017):

@bkcsoft I updated the issue, seems almost done. 😄

@lunny commented on GitHub (Dec 31, 2017): @bkcsoft I updated the issue, seems almost done. 😄

GiteaMirror commented

@stevegt commented on GitHub (May 5, 2018):

Mentioning #3076 (add github compatible v3 routes) here for searchability.

@stevegt commented on GitHub (May 5, 2018): Mentioning #3076 (add github compatible v3 routes) here for searchability.

GiteaMirror commented

@Serkan-devel commented on GitHub (Mar 24, 2019):

Will the GraphQL-API be supported?

@Serkan-devel commented on GitHub (Mar 24, 2019): Will the GraphQL-API be supported?

GiteaMirror commented

@lunny commented on GitHub (Mar 25, 2019):

There is an issue to report that.

@lunny commented on GitHub (Mar 25, 2019): There is an issue to report that.

GiteaMirror commented

@6543 commented on GitHub (Nov 24, 2020):

beside api unrelated & feed API, everything is here.

should we close this now?

@6543 commented on GitHub (Nov 24, 2020): beside api unrelated & feed API, everything is here. should we close this now?

GiteaMirror commented