Elizabeth Craig

I think this is already possible with the existing implementation. The package name should be accessible via `PackageChangelogRenderInfo.newVersionChangelog.name`, and then you can conditionally modify rendering as needed.

I think potentially both could be useful in different scenarios. Maybe have it as an option for which one to use?

I don't think `dependentChangeType` is intended to be specified in the beachball config. If you need to override it at all (which is very rare) that would only be done...

Hmm apparently I found one of the special cases myself, #582. 😆 But needing to override it beyond the scope of a single package should be even more unusual.

That makes sense. I think it works today as an unintended side effect of the way configs specified for the repo and on the CLI are merged (we just blindly...

In Fluent UI we use [syncpack](https://www.npmjs.com/package/syncpack) to help prevent this type of issue (though obviously having beachball handle it better would be good). Here's our [syncpack config](https://github.com/microsoft/fluentui/blob/master/package.json) for reference if...

Manually editing the JSON would probably work. I think the comments from the JSON are just dumped straight into the markdown changelog.

This may have been fixed in #539. Can you check with the latest beachball version?

One workaround for this right now (besides reverting the commit) is that you can run `beachball change --no-commit` or add `commit: false` to your beachball config. That way it will...

Thinking about it more, I'm not sure this is something that ought to be added as a repo config option, though it might be reasonable to support as a command...