Thanks for the feedback, glad that did is helpful! Implementing releases should not be difficult although it seems that the API does not provide much filtering options:

• https://docs.github.com/en/rest/releases/releases

However, all important information (such as uploader or published_at timestamp) seems to be there, for example here's the output for all tmt releases:

• https://api.github.com/repos/teemtee/tmt/releases

Feel free to file a pull request with the new release stats! :)

Other github plugin stats can serve as an inspiration:

I see, thanks for the pointers!

Am I right that I would need to recursively query all repositories that the user has access to in order to retreive if they created a new release? How can I do this? Or is there another, better way?

Unfortunately it looks like that. Unless there is another API call which would allow searching across projects. I haven't found one in the list. One way could be to provide a list of active projects in the config. It could look like this:

[github]
type = github
login = psss
url = https://api.github.com/
projects = psss/did, teemtee/fmf, teemtee/tmt

Then we would check only these relevant ones.

One way could be to provide a list of active projects in the config. It could look like this:

[github]
type = github
login = psss
url = https://api.github.com/
projects = psss/did, teemtee/fmf, teemtee/tmt

Then we would check only these relevant ones.

Makes sense 👍

Since I only want to add releaeses logging and not modify existing logic, maybe projects should be named releaseProjects or something so that it is clear that this is only meant for the releases stats or WDYT?

I'd vote for something short, and projects could be possibly useful for other stats as well in the future.

I'd vote for something short, and projects could be possibly useful for other stats as well in the future.

All right