Naming update for Stacks rebrand #841 #900
Merged
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
|
@friedger is attempting to deploy a commit to the Blockstack Team on Vercel. A member of the Team first needs to authorize it. |
9 tasks
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.
Description
This PR replaces the use of the name
BlockstackwithStackswhere it makes sense.Some naming changes require an additional noun like
Blockstackin the context of authentication becomesStacks Auth.For details refer to issue #841
This PR contains the same changes as fd5b3c8
Type of Change
Does this introduce a breaking change?
No
Are documentation updates required?
No
Testing information
Nothing special
Checklist
npm run testpasses