Ideal handling for a CHANGELOG that is larger than Github's (et al.) rendering size? #657

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Open

corsonknowles opened this issue Apr 8, 2025 · 0 comments

corsonknowles commented Apr 8, 2025

Hi team,

We were wondering if you have some suggestions on how to best deal with CHANGELOGs that have grown to a very large size.

See screenshots here:

Github crashes loading our CHANGELOG due to length/size rubocop/rubocop#14011

Currently considering a 5 year split and interlinking files as our solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment