-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
[API] Best way for issues and PRs and it's count #6774
Labels
issue/confirmed
Issue has been reviewed and confirmed to be present or accepted to be implemented
modifies/api
This PR adds API routes or modifies them
Comments
mmarif4u
changed the title
Best way for issues and PRs and it's count
[API ]Best way for issues and PRs and it's count
Apr 27, 2019
mmarif4u
changed the title
[API ]Best way for issues and PRs and it's count
[API] Best way for issues and PRs and it's count
Apr 27, 2019
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions. |
lunny
added
the
issue/confirmed
Issue has been reviewed and confirmed to be present or accepted to be implemented
label
Jun 26, 2019
with #12275 |
@6543 I guess this is pretty much resolved. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
issue/confirmed
Issue has been reviewed and confirmed to be present or accepted to be implemented
modifies/api
This PR adds API routes or modifies them
Gitea 1.8.0
Currently reop info API return open issue count of issues.
https://try.gitea.io/api/swagger#/repository/repoGet
While issues API return both PRs and issues.
https://try.gitea.io/api/swagger#/issue/issueListIssues
If let's say there are 10 open issues and 2 open PRs, open issue count is 10. While issues API return 12 records inlcuding PRs.
Just an idea, inlucde the open PRs in the count OR exlucde PRs from the issues API.
The text was updated successfully, but these errors were encountered: