github-tools / github-tools/github-release-notes

How to use gren for private repo and django/react app?

Offen
#193 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
help wanted
Vorherrschende Sprache
JavaScript
Sterne
897
Forks
313
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

I have a private repo in Github which uses django for backend and react for frontend

I like to have my changelog exposed to my endusers as well.

If I expose my changelog to endusers AND I use gren, this will certainly force me and my team to write better commit messages.

I typically handwrite the changelog into html markup for the changelog to show up in the app. And typically it's just a long html page with the contents arranged like this:
```
v0.11.0 (yyyy-mm-dd)

- something
- another thing

v0.10.2 (yyyy-mm-dd)

- something
- another thing

and so on...
```

What's the output of running gren so that I can transpile it into the format I need to show to endusers?

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

No file, test, or entry point is named. Start by checking gren's generated release-note output and its handling of private repositories; done means documenting whether that output can be transformed into the requested HTML changelog format.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
django, javascript, react
Bereich
documentation, release
Issue-Typ
Dokumentation
Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Aktivitätsstatus
Veraltet
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
25/100

Neue Issues direkt in Ihr Postfach

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