-
Notifications
You must be signed in to change notification settings - Fork 218
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.
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
feat: implement scoped changelogs #421
Conversation
for the context: in flutterfire we have a bunch of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks basically good. I've cleaned up a few things, made CI pass and added docs.
docs/configuration/overview.mdx
Outdated
|
||
The path to the changelog file relative to the workspace root. | ||
|
||
### `command/version/changelogs/scope` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you think maybe we should have the same syntax as properties under select-package
in melos run scripts?
Will allow all filter types then rather than just scope, and will be consistent with other areas
Should just be able to reuse most of the logic to do so?
Thoughts @blaugold?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point! I think we should do that.
No description provided.