-
Notifications
You must be signed in to change notification settings - Fork 8
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
Docs: Add hint to @comet/upgrade #1637
Conversation
dkarnutsch
commented
Jan 30, 2024
- Add changeset (if necessary)
I would add the command in the migration guide everyone has to execute when upgrading. This is not optional. And I would also remove all references in the migration guide to stuff that is done automatically with it. (We also have a changelog that should mention those renames) the shorter the better |
e737c27
to
e3a772d
Compare
@nsams like that? |
yes, but I would even see it as part of every single migration guide |
the migration guide should be like a tutorial |
Yes, but IMO that doesn't mean we can't have some general information about the upgrade process in other parts of the docs. Also we don't have a direct reference to the comet-upgrade repo in the migration guide |
That was my intention. So I think this PR is alright as it is as it addresses a different part. |