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

Build Out Missing API Components #55

Closed
7 tasks done
jag3773 opened this issue Jun 1, 2016 · 9 comments
Closed
7 tasks done

Build Out Missing API Components #55

jag3773 opened this issue Jun 1, 2016 · 9 comments
Assignees
Labels

Comments

@jag3773
Copy link
Contributor

jag3773 commented Jun 1, 2016

Potentially, there are missing features in the API that we need to implement in order to support current translationStudio needs and future translationManager needs. We need to discuss this with @klappy and @neutrinog to see what they think.

Here is a list for starters:

  • Users
  • Starring - we need to get read/write what repos a user has starred
  • Watching - need read/write for what repos a user is watching
  • Issues - we need API support to add, edit, close, remove issues
  • Organization functions - We need to add, modify, delete members, teams, webhooks.
  • Webhooks - we need full API support to add, modify, remove webhooks for repos or organizations
  • Repository functions - We need to be able to modify repo configuration, such as create/modify Releases, manage collaborators, create fork, etc.

I believe current progress is recorded in https://github.com/gogits/go-gogs-client/wiki.

@da1nerd
Copy link

da1nerd commented Jun 2, 2016

I'm throwing word count in here just so we/I don't forget.

@jag3773
Copy link
Contributor Author

jag3773 commented Jun 13, 2016

@neutrinog I don't think the Gogs API would show word counts would it? I thought that was going to be in the resource container or the Door43 catalog.

@da1nerd
Copy link

da1nerd commented Jun 13, 2016

@jag3773 yes sorry I wrote that before I realized what this issue was really about :P

@ethantkoenig
Copy link
Contributor

ethantkoenig commented Oct 19, 2016

@jag3773 Could you be a little more specific about the endpoints you would like me to add? For example, "Issues" is in the checklist above,but there are already a number of API endpoints for issues (see the wiki). Are there additional ones that you need?

@jag3773 jag3773 added the Gogs label Nov 17, 2016
@ethantkoenig
Copy link
Contributor

ethantkoenig commented Nov 17, 2016

@jag3773 Do we need to support removing issues, as opposed to just closing them? Right now, neither Github nor Gogs/Gitea support removing issues (neither in the API, nor from a browser).

@ethantkoenig
Copy link
Contributor

I believe that the endpoints we need for issues already exist (see Issues). Let me know if I'm missing something.

@jag3773
Copy link
Contributor Author

jag3773 commented Nov 19, 2016

If it's there, great!

@ethantkoenig
Copy link
Contributor

Checking off webhooks, because the endpoints already exist for repos, and the ones for organizations are covered by the "Organizations" item.

@ethantkoenig
Copy link
Contributor

@jag3773 All of the requested endpoints have been merged into gitea:master.

@jag3773 jag3773 closed this as completed Jan 17, 2017
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants