Skip to content
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(error-reporting): improve clarity for opt-out folks #3876

Merged
merged 2 commits into from
Nov 21, 2017

Conversation

paulirish
Copy link
Member

fixes #3854

  • docs clarity around "opt-out" and all that.
  • include docs link from --help
  • show docs link before providing CLI prompt

@@ -59,7 +59,7 @@ function getFlags(manualArgv) {
'Configuration:')
.describe({
'enable-error-reporting':
'Enables error reporting (prompts once by default, setting this flag will force error reporting to that state).',
'Force enables error reporting. --no-enable-error-reporting will force disable. More: https://git.io/vFFTO',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Force enables" sounds like a Jedi move. How about "Enables error reporting, overriding any saved preference...."

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Enables error reporting, overriding any saved preference. --no-enable-error-reporting will do the opposite. More: https://git.io/vFFTO

@wardpeet
Copy link
Collaborator

should we never prompt again or after x weeks or after each new release?

@paulirish
Copy link
Member Author

should we never prompt again or after x weeks or after each new release?

I'm into the idea of prompting again if we hit that 20sec timeout, but also it may not matter with enough scale.

@paulirish paulirish merged commit 9d312c2 into master Nov 21, 2017
@paulirish paulirish deleted the sentrypromptchange branch November 21, 2017 21:16
@paulirish
Copy link
Member Author

Should we ship a quick 2.6.1 with this and Brendans new PR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Document --no-enable-error-reporting and CI env var
4 participants