Added instruction to remove PRIVATE KEY from README #251
Conversation
This file contains 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
|
@vojtechjelinek and @jameesjohn Sir, Please review this PR. Thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Explanation
Users or contributors have to remove PRIVATE KEY from Readme.md in order to use Oppiabot Locally Since PRIVATE KEY gets automatically detected by .pem file. But this gets overlooked since it is mentioned in one of the various comments in .env file. I personally faced this difficulty and also seen some of the other contributors facing the same. I asked it on the Gitter and took more than 1 day to resolve this. This might not be a big addition but will definitely prove helpful to new contributors.
Checklist