Pepco example

[bretwalker]

This is an example of what's required to set up a new scraper.

Read more about why this data can be useful and how it can be made available here:
https://codeforkentuckiana.org/2019-12-18-power-utility-data/

If this repo is cloned, lgeku_scraper.py can be replaced with another location-specific scraper, like the one in this PR.

instance_id and view_id come from the outage map's HTML:
https://kubra.io/stormcenter/views/66f63a73-3b4a-4b2a-a833-f01668ef4986
which is iframed in:
https://www.pepco.com/Outages/CheckOutageStatus/Pages/ViewOutageMap.aspx

owner and repo need to be set to the repo where the outage JSON should be written.

The only other thing to do is to add a GitHub token to the cloned repo's Actions so that it can write to the destination repo.

1. Create a personal access token using an account that has access to the destination repo: https://help.github.com/en/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line
2. Add it to GitHub actions, giving it the name GH_TOKEN: https://help.github.com/en/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets

The action should have been copied over and should be picked up and execute an Action every 15 minutes, scraping and saving the current outages.