API should list commits #2451

New Issue

GiteaMirror · 2025-11-02T04:36:43-06:00

GiteaMirror commented

2025-11-02 04:36:43 -06:00

Originally created by @lunny on GitHub (Oct 25, 2018).

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

List commits (just like GitHub)

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

number of commits in a repo

splitted from #760

Originally created by @lunny on GitHub (Oct 25, 2018). This is a feature request for the API to support more details for reporting. I would like to access: - List commits (just like [GitHub](https://developer.github.com/v3/repos/commits/#list-commits-on-a-repository)) This would enable reporting integration to query the api to determine, over a period: - number of commits in a repo splitted from #760

GiteaMirror added the issue/confirmed modifies/api labels 2025-11-02 04:36:43 -06:00

GiteaMirror closed this issue

2025-11-02 04:36:44 -06:00

GiteaMirror commented

2025-11-02 04:36:44 -06:00

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

I'm currently working on it (only the GET-Part b/c see following:)
The CommitAPI depends on the TreeAPI so I woun't be able to fully implement it until #4185 is done.
POSTing a commit will be absolutely postponed until the TreeAPI is done as it doesn't make sense to create an commit without a tree object.

@HoffmannP commented on GitHub (Oct 25, 2018): I'm currently working on it (only the GET-Part b/c see following:) The CommitAPI depends on the TreeAPI so I woun't be able to fully implement it until #4185 is done. POSTing a commit will be absolutely postponed until the TreeAPI is done as it doesn't make sense to create an commit without a tree object.

GiteaMirror commented

2025-11-02 04:36:45 -06:00

@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.

GiteaMirror commented

2025-11-02 04:36:45 -06:00

@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.

GiteaMirror commented

2025-11-02 04:36:45 -06:00

@richmahn commented on GitHub (Jul 23, 2019):

@HoffmannP #4185 has been merged and closed, so it is done.

@richmahn commented on GitHub (Jul 23, 2019): @HoffmannP #4185 has been merged and closed, so it is done.

GiteaMirror commented

2025-11-02 04:36:45 -06:00