[NPMCLI-101] Rename mgnl setup to mgnl customize-local-config Created: 10/Feb/17  Updated: 16/Feb/17  Resolved: 16/Feb/17

Status: Closed
Project: Magnolia CLI
Component/s: None
Affects Version/s: 2.0
Fix Version/s: 2.0

Type: Improvement Priority: Neutral
Reporter: Robert Kowalski Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Documentation update required:
Yes
Date of First Response:
Sprint: Basel 83
Story Points: 3

 Description   

mgnl setup is confusing to new users as it looks like a necessary step after getting the CLI.

We (czimmermann fgrilli rkowalski) decided to rename it to `customize-local-config`

Its a command for a very special use case, so shorter versions, like "customize" weren't a good fit.

Bonus points for supporting both `customize-local-config` and `customise-local-config`, but just one of them visible in the help



 Comments   
Comment by Robert Kowalski [ 10/Feb/17 ]

should land in 2.0 as its a breaking change anyway

Generated at Mon Feb 12 04:46:32 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.