Update import.md to use release tag when importing from GitHub #2634
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
Update GitHub import instructions to use a release tag where available and change the example of importing from OpenZeppelin Contracts to use an official release rather than the master branch.
Update console import instructions to use a release tag where available and change the example of importing from OpenZeppelin Contracts to use an official release rather than the master branch.
Closed
yann300
approved these changes
Apr 7, 2020
|
Thanks @abcoathup for this PR. I appreciate you catching this issue and making the update! |
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.
Update GitHub import and console import instructions to use a release tag where available and change the example of importing from OpenZeppelin Contracts to use an official release rather than the master branch. This is to avoid the community from using code outside of an official release.
I use the following example and note on the OpenZeppelin Community Forum:
https://forum.openzeppelin.com/t/deploy-a-simple-erc20-token-in-remix/1203