You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since this is now a mono-repo, changelogs are even more criticial to see whats been done in an add-on.
addons-actions is now at version 3.2.0 but the changelog only goes up to 1.x. Please either update the changelog file or remove it. Or better yet, split the add-ons back into separate repos but still under the storybook org
The text was updated successfully, but these errors were encountered:
Hey @eddiemonge,
There's a changelog in a subproject? Well that'd be legacy content. I guess we could remove it, it's probably no use to anyone anymore..
The monorepo is helping us tremendously in our development, it's not changing. Thanks for the suggestion though, I understand it's not quite the industry standard.
Although projects like babel, webpack, jest also doing it this way, so perhaps it kinda is?
In any case, keep the suggestion coming! We can definitely do with some improvements on the codebase. There's still old examples dev-setups and indeed -as you point out- changelogs laying around from before the monorepo merge.
We want to clean all this up. but at the same time we're careful and want to focus on the things that actually matter. So some things will only get a cleanup if we find the spare time, just feel like cleaning up or it bothers us.
Since this is now a mono-repo, changelogs are even more criticial to see whats been done in an add-on.
addons-actions is now at version 3.2.0 but the changelog only goes up to 1.x. Please either update the changelog file or remove it. Or better yet, split the add-ons back into separate repos but still under the storybook org
The text was updated successfully, but these errors were encountered: