[API] Issue events #285

Closed
opened 2025-11-02 03:17:19 -06:00 by GiteaMirror · 11 comments
Owner

Originally created by @qistoph on GitHub (Jan 25, 2017).

This is a feature request for the API to support more details for reporting. I would like to access:

  • Issue events (just like GitHub)

This would enable reporting integration to query the api to determine, over a period:

  • number of issues closed
Originally created by @qistoph on GitHub (Jan 25, 2017). This is a feature request for the API to support more details for reporting. I would like to access: - Issue events (just like [GitHub](https://developer.github.com/v3/issues/events/)) This would enable reporting integration to query the api to determine, over a period: - number of issues closed
GiteaMirror added the type/featureissue/stalemodifies/api labels 2025-11-02 03:17:19 -06:00
Author
Owner

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

Related to #64

@bkcsoft commented on GitHub (Jan 29, 2017): Related to #64
Author
Owner

@ghost commented on GitHub (Aug 23, 2018):

Gitea doesn't have an API call to list commits still? Or am I missing something?

@ghost commented on GitHub (Aug 23, 2018): Gitea doesn't have an API call to list commits still? Or am I missing something?
Author
Owner

@Coriou commented on GitHub (Aug 24, 2018):

Also wondering the same thing. I think it's not possible right now, or undocumented. I'll keep looking for a way

@Coriou commented on GitHub (Aug 24, 2018): Also wondering the same thing. I think it's not possible right now, or undocumented. I'll keep looking for a way
Author
Owner

@HoffmannP commented on GitHub (Oct 25, 2018):

Can we please split this issue into two?
A issue events
B list commits

@HoffmannP commented on GitHub (Oct 25, 2018): Can we please split this issue into two? A issue events B list commits
Author
Owner

@lunny commented on GitHub (Oct 25, 2018):

@HoffmannP I think A has been implemented but B is not.

@lunny commented on GitHub (Oct 25, 2018): ~@HoffmannP I think A has been implemented but B is not.~
Author
Owner

@HoffmannP commented on GitHub (Oct 25, 2018):

Can we rename this issue then? Alternativly close and reopen?

@HoffmannP commented on GitHub (Oct 25, 2018): Can we rename this issue then? Alternativly close and reopen?
Author
Owner

@lunny commented on GitHub (Oct 25, 2018):

@HoffmannP I think I'm wrong. Neither are implemented.

@lunny commented on GitHub (Oct 25, 2018): @HoffmannP I think I'm wrong. Neither are implemented.
Author
Owner

@lunny commented on GitHub (Oct 25, 2018):

@HoffmannP done.

@lunny commented on GitHub (Oct 25, 2018): @HoffmannP done.
Author
Owner

@HoffmannP commented on GitHub (Oct 25, 2018):

Wow, that was solved in record time! Thanks

@HoffmannP commented on GitHub (Oct 25, 2018): Wow, that was solved in record time! Thanks
Author
Owner

@stale[bot] commented on GitHub (Jan 5, 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.

@stale[bot] commented on GitHub (Jan 5, 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.
Author
Owner

@stale[bot] commented on GitHub (Feb 23, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Feb 23, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#285