Repository navigation
Improve init command #160
Description
I'm thinking now that we have a JSON config, we could have the init command ask the user and write the config that they want.
The flow I'm thinking:
- Do you want to generate changelogs? If so, which changelog entry generator would you like to use?
- No, I don't want changelogs
- Yes, I want changelogs with GitHub info (depends on Create changelog entry generators for common use cases #159)
- Yes, I want changelogs with only commits
- Would you like Changesets to commit changesets and version/changelog updates for you?
- Should packages be published publicly or privately?
Activity
Noviny commentedon Sep 17, 2019
This makes sense to me. I think #159 for common use-cases is probably higher priority though - wouldn't mind shipping some basic ones before making it obvious options
emmatown commentedon Sep 18, 2019
Yes, 100%. I'm probably going to do #159 and then this issue after.
chengyixu commentedon Mar 20, 2026
Hi! I'd like to work on this.
Approach: I'll enhance the
initcommand to use an interactive prompt (via@changesets/get-configor similar) that walks users through: (1) changelog preference (none / GitHub-linked / commits only), (2) whether to auto-commit changesets and version bumps, and (3) public vs private publish scope. The answers will be serialized into.changeset/config.jsonso the project is fully configured from the start.Timeline: 2-3 days
Background: Node.js/TypeScript specialist, 35+ npm packages, extensive monorepo and changeset release automation experience.
— @chengyixu