Feature Request (size: Large-ish) - REPO cards

[hesreallyhim]

Description

Repo cards have a kind of "second-class" status in this project, one might argue. They are called "pins" because they tend to reflect statistics about a repo in relation to a user (like the cards that are "pinned" to a user profile.

Feature Proposal

I'd like to have cards that have repo stats - stats that are agnostic with respect to any individual user. What kind of stats? Creation date, date of last commit, stars, forks, open issues/PRs... the API exposes a lot of stats.

Implementation Suggestion

Based on my understanding of the project, the pins endpoint is not really meant for this kind of use case. Rather than try to place more of a burden on /pin/, I think a better approach is a new endpoint, /repo/.

Comments

I implemented some additional repo metrics in order to serve my particular use case. But that's a pretty unusual setup. It's possible that this is not something that would be of general interested. On the other hand, I can imagine some other use cases.

[martin-mfg]

I agree that the name "pin" is surprising for users who want to show repo stats in general instead of pinning their repos to their personal readme. However, by default the generated card contains only stats which are not specific to a particular user, e.g. the number of stars and forks. In fact the only case I can think of where pin cards "reflect statistics about a repo in relation to a user" is this new feature.

I agree that we should add support for more repo stats like "creation date, date of last commit, stars, forks, open issues/PRs...". Since they are comparable to existing general repo stats like star count and fork count, I actually think these new stats would fit nicely into the existing /pin endpoint. With the /pin endpoint supporting the show parameter now, we could use show to enable each of the additional repo metrics individually. And/or we could add a layout parameter which enables a bigger group of the new stats at once.

I implemented some additional repo metrics in order to serve my particular use case. But that's a pretty unusual setup.

I actually have better support for use cases like yours already on my ideas list because I think it is a valueable addition. And it would be great if you could create a PR in this repo to add (some of) the stats you mentioned! But as I mentioned here, getting new features merged is currently not the top priority, so it might take some time to merge such a PR.