Switch to unclog
to parallelize changelog updates
#891
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As per out-of-band discussions, we noticed that we often end up in a situation where we're working on several PRs simultaneously, each of which modifies the
CHANGELOG.md
file but makes changes to distinct parts of the code base. This inevitably results in annoying merge conflicts purely related to the changelog.The simplest solution seems to be to disaggregate changelog entries and build
CHANGELOG.md
from those entries as we perform a release.For this, I built unclog, which is a small CLI tool written in Rust, to help manage these disaggregated changelog entries.
.changelog/