You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Starter kits are most useful when they're actively maintained, users need a way to know if the kit is maintained, or not
Describe the solution you'd like!
Add a "Last Commit" badge next to each included repo so users can see if the repo is active or not. This can be done easily and in an automated way via Sheilds - see link.
We could add this to a contributor.md file as a requirement for folks to include their starter kit .
Might also be worth adding more contextual data badges like number of contributors, downloads etc. if possible
Have you considered any alternatives?
No, think this is the default best solution but not precious if there is a better option for this.
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
The docs show how to do this simply, just add this to the MD - ![GitHub last commit (by committer)](https://img.shields.io/github/last-commit/:user/:repo)
Contact Details
No response
Is your feature request related to a problem? Please describe.
Starter kits are most useful when they're actively maintained, users need a way to know if the kit is maintained, or not
Describe the solution you'd like!
Add a "Last Commit" badge next to each included repo so users can see if the repo is active or not. This can be done easily and in an automated way via Sheilds - see link.
We could add this to a contributor.md file as a requirement for folks to include their starter kit .
Might also be worth adding more contextual data badges like number of contributors, downloads etc. if possible
Have you considered any alternatives?
No, think this is the default best solution but not precious if there is a better option for this.
Code of Conduct
The text was updated successfully, but these errors were encountered: