fedi/forgejo - git.minimally.online

fedi/forgejo

mirror of https://codeberg.org/forgejo/forgejo.git synced 2024-11-28 15:37:35 +00:00

2 lines

182 B

Markdown

Raw Normal View History

docs(release-notes): split items in files to avoid conflicts (#3452) 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>

2024-04-26 08:26:33 +00:00

Save updated empty comments instead of skipping the update silently, [which prevented the removal of attachments of such comments](https://codeberg.org/forgejo/forgejo/issues/3424).