API data update from PokeAPI/pokeapi#395
Closed
pokeapi-machine-user wants to merge 1 commit into
Closed
Conversation
pokeapi-machine-user
force-pushed
the
staging
branch
from
812aa47 to
f500334
Compare
pokeapi-machine-user
changed the title
PokeAPI/pokeapi#1587PokeAPI/pokeapi
pokeapi-machine-user
force-pushed
the
staging
branch
from
f500334 to
4d85632
Compare
pokeapi-machine-user
changed the title
PokeAPI/pokeapiPokeAPI/pokeapi#1588
pokeapi-machine-user
force-pushed
the
staging
branch
from
4d85632 to
d1933e1
Compare
pokeapi-machine-user
changed the title
PokeAPI/pokeapi#1588PokeAPI/pokeapi
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
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.
Incoming data generated by PokeAPI/pokeapi's CircleCI worker.
The new data was generated using a copy of PokeAPI/pokeapi repository when the
HEADwas pointing to3db9c2c2e1bb1a2f7a5eaa6843964dcabb001010.This Pull Request should have been deployed in our staging environment, check here for the lastest build timestamp and status code.