opened
mllemango
username_0
<!--
  ☝️How to write a good PR title:
  - Prefix it with [Feature] (if applicable)
  - Start with a verb, for example: Add, Delete, Improve, Fix…
  - Give as much context as necessary and as little as possible
  - Prefix it with [WIP] while it’s a work in progress
-->

### WHY are these changes introduced?

Fixes #861  <!-- link to issue if one exists -->

<!--
  Context about the problem that’s being addressed.
-->

### WHAT is this pull request doing?

**Adding subcommand `analytics`** to `config` 
Allows users to opt in/out of anonymous usage reporting
![image](https://user-images.githubusercontent.com/30154753/94488501-b657a080-01b0-11eb-8d0f-6f2ceb9dbc76.png)


<!--
  Summary of the changes committed.
  Before / after screenshots appreciated for UI changes.
-->
Melanie/analytics opt in out
issue
created
gfscott
username_1
### Enable or disable
$ shopify config analytics --enable
$ shopify config analytics --disable
```

Again, probably not something for this PR, just wanted to flag it!
comment
created
paulomarg
username_2
One thing to keep in mind is that this command is hidden for now AFAIK. Should we start making it visible (which would reveal the configs for features as well)?
comment
created
tanema
username_3
You can just run `shopify config analytics` and see the status of the config
comment
created
gfscott
username_1
I think if there's a command present in the tool, we should default to documenting it officially — only omitting if there's an especially compelling reason. To me, analytics opt-in/opt-out is additionally a matter of user trust, so it deserves to be included in the standard command reference.
comment
created
mllemango
username_0
Will follow up with a separate PR to update documentation
comment