Update documentation for upgrading lead to be a user #418
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jonnyom
approved these changes
Aug 22, 2018
Contributor
jonnyom
left a comment
jonnyom
left a comment
There was a problem hiding this comment.
This looks good to me. Thanks for this!
Contributor
Author
Contributor
|
@andrewhavens let me take a look at that and get back to you on this 👍 |
Contributor
|
@andrewhavens hope my explanation of what is going on in #419 makes sense. I'll merge this for you and make a separate update to the README to explain the best way to do this conversion. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have updated the example in the documentation to be less vague about how to convert a lead to be a user. I got the code for this from this comment.