mirror of
https://codeberg.org/forgejo/forgejo.git
synced 2024-12-23 07:43:18 -05:00
127eff49ee
I thought there would be conflicts but that they would not be so difficult to manage. Worst idea I had this week. Change to @oliverpool idea instead. > Instead of documenting the release notes in the issue, why not in the codebase? > > For instance in [go](https://cs.opensource.google/go/go/+/master:doc/README.md) there is a `doc/next` folder where you add `<pr-number>.md` files which document each pr. > > Before the release, a script takes all those files to generate the changelog. > > Having them as a file tracked by git, makes them easy to review and to programmatically handle. Refs: https://codeberg.org/forgejo/discussions/issues/155#issuecomment-1787013 Co-authored-by: Shiny Nematoda <snematoda.751k2@aleeas.com> Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/3452 Reviewed-by: Gergely Nagy <algernon@noreply.codeberg.org> Co-authored-by: Earl Warren <contact@earl-warren.org> Co-committed-by: Earl Warren <contact@earl-warren.org>
1 line
224 B
Markdown
1 line
224 B
Markdown
The regression in the [`fogejo admin user create`](https://forgejo.org/docs/v7.0/admin/command-line/#admin-user-create) CLI command [is fixed](https://codeberg.org/forgejo/forgejo/issues/3399) and it is backward compatible.
|