countries-states-cities-database VS git-auto-commit-action

At $WORK I created a prototype that used https://github.com/dr5hn/countries-states-cities-database for a city/state/country typeahead widget - it was generally ok, loaded data into a read-only sqlite db that was created at container build time. We shipped it to AWS for the demo. There are some data bugs, cities in Turkey and Geneva were the top reported issues. You get what you pay for I suppose. Have not seen Geonames before this post but agree the username vs some form of api key/auth is weird.

This looks promising.. https://github.com/dr5hn/countries-states-cities-database

Depending on what you need from this package, this might be of help https://github.com/dr5hn/countries-states-cities-database

Link

The latter one, though, says that it got its data from countries-states-cities-database, which has some json files with the countries, states and cities. The cities json file is huge. I really don't think that I would ever use all of them, I would only need data from North and South America, at most.

We are also using the auto-commit action to commit the changes. We can configure the commit message and other options. Read more about the auto-commit action here. This is optional - we can also use the git action to commit the changes manually.

commit and push the changes, if any.

Stefan Zweifel - Committing the changes file from a workflow

If you want to see a real world example I encourage you to take a look at the tests I've written for git-auto-commit. You can find them on GitHub.