getsentry / getsentry/sentry-dotnet

Consider moving unreleased changes to a separate "Unreleased.md" file

Open
#4,755 3 comments 0 reactions 0 assignees View on GitHub
.NET Repository Maintenance State: Needs Discussion Task
Dominant language
C#
Stars
770
Forks
248
Avg merge
3d 4h
Merged PRs (30d)
49

Description

Perhaps we can think of a different way of adding entries to the `CHANGELOG.md`, as this is most commonly the merge conflict ... maybe we don't add it directly, but place it "somewhere" from where it's then pushed to the `CHANGELOG.md` in the correct place when (squash) merging 🤔 ... something for us to think about.

_Originally posted by @Flash0ver in https://github.com/getsentry/sentry-dotnet/issues/4724#issuecomment-3551799515_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.