anuraghazra / anuraghazra/github-readme-stats

Development has moved to github-stats-extended.

Offen
#4,902 1 Kommentar 12 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
JavaScript
Sterne
79.8k
Forks
37.7k
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

Hi everyone,

maintenance activity in this project has been limited for some time. To keep the project usable and to add new features, active development has moved to [github-stats-extended](https://github.com/stats-organization/github-stats-extended). This extended version of github-readme-stats is being maintained by @marcalexiei and me, with help from the community and from @rickstaa, one of the maintainers of github-readme-stats.

We want to keep this great project alive, but since the current maintainers in the github-readme-stats repository have only limited access rights, adding contributors here and keeping the original Vercel deployment stable has become impossible.

**We encourage everyone to switch to [github-stats-extended](https://github.com/stats-organization/github-stats-extended) for new features, fixes and a stable Vercel deployment.**

To quickly migrate to github-stats-extended, see [here](https://github.com/stats-organization/github-stats-extended#migration-from-github-readme-stats). For a list of new features in github-stats-extended see [here](https://github.com/stats-organization/github-stats-extended/blob/master/docs/fork.md). We also maintain [github-readme-stats-action](https://github.com/stats-organization/github-readme-stats-action), a GitHub Action which creates your stats cards in a GitHub workflow instead of fetching them from a Vercel server.

Finally, we want to thank @anuraghazra and everyone else who worked on github-readme-stats over the years!

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

This is a maintenance notice rather than a code task; start with the linked github-stats-extended migration guide and docs/fork.md. Done means understanding the migration path and using the maintained repository for future fixes and features.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
github, github-actions, javascript
Bereich
documentation, release
Issue-Typ
Dokumentation
Schwierigkeit
1/5
Geschätzter Aufwand
Unter einer Stunde
Aktivitätsstatus
Veraltet
Klarheit
Muss geklärt werden
Anfängerfreundlichkeit
15/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.