This repository has been archived by the owner on Jul 3, 2022. It is now read-only.
adding Fernando Sosa token #26565
Closed
adding Fernando Sosa token #26565
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Please note: This repository is being rebuilt to accept the new volume of token additions and modifications. PR merges will be delayed.
I agree to not ping anybody on Discord/Twitter/email about this pull request. Instead I will inquire by posting a new comment in the pull request if needed.
PRs are reviewed in bulk and and can take up to two weeks to be merged.
This repository is managed using an auto merge action. Please ensure your PR has no deleted lines, and it will be merged.
Please provide the following information for your token.
Please include change to the
src/tokens/solana.tokenlist.jsonfile in the PR.DON'T modify any other token on the list.
At minimum each entry should have
Auto merge requirements
Your pull request will be automatically merged if the following conditions are met:
Your pull request only adds new tokens to the list. Any modification to existing
tokens will require manual review to prevent unwanted modifications.
Your pull request does not touch unrelated code. In particular, reformatting changes to unrelated
code will cause the auto merge to reject your PR.
Any asset files added correspond to the token address you are adding. Asset files
must be PNG, JPG or SVG files.
Your change is valid JSON and conforms to the schema. If your change failed validation,
read the error message carefully and update your PR accordingly.
No other tokens shares the same name, symbol or address.
For example, this change would be rejected due to unrelated changes:
The bot runs every 60 minutes and bulk-merges all open pull requests to prevent conflicts.
This means that you need to wait up to 60 minutes for your pull request to be merged or reprocessed.