Rebranding / renaming the GitHub Organization and Possibly this Repo's Name

[allella]

@ramonaspence @oliviasculley since we've changed the GitHub org from codeforgreenville or hackgvl, it's useful to update our local Git configurations.

GitHub provides some examples on updating a remote URL but I think editing .git/config in a local repo should also do the trick and is possibly easier.

Additionally, I'd like to propose we rename this repo from _upstate_tech_calservice to events-api

Also, if the https://github.com/hackgvl/eventsbot repo is only going to do things related to Slack, then it may avoid some confusion to include the word "slack" in that repo name, like slack-events-bot

Thoughts?

[oliviasculley]

This sounds good, I've renamed the eventsbot to slack-events-bot, but I haven't renamed the docker image for it yet. Please let me know if you'd like me to rename that, since the docker-compose.yml on the hosted location will most likely need to change as well

[allella]

Yeah, I think it would be good to rename the Docker image too.

Since we're using mostly dashes for spaces in repo names, I think we can stick with that going forward so our repos don't look inconsistent like with the CFG ones did over time.

[allella]

@zach2825 just a general notes that we've renamed the GitHub org and even some of the repo names.

This repo is going to be renamed too.

[allella]

@ramonaspence @oliviasculley the Events API repo name is now https://github.com/hackgvl/events-api/

We should update our "upsteam" .git/config branch URls in our local cloned copies to the new URL path.

And, it may be good to rename our forks of this repo so they are /events-api too.