Github integration - issue/project card creation

[adamkendis]

Related to #447

• Added redacted Github-related vars to server config example file.

• Implemented FeedbackService for /feedback route. Creates issue via Github API and adds the issue to 311Data-Support project board.

• Implemented /feedback route. Receives POST containing form data from front-end 'Contact' page.

  • Up to date with dev branch
  • Branch name follows guidelines
  • All PR Status checks are successful
  • Peer reviewed and approved

[jmensch1]

Looks tight to me. Russell might wanna have a look.

How come the PROJECT_URL is redacted but the ISSUES_URL is not? just curious

[adamkendis]

PROJECT_URL contains a project ID that is only available via an authenticated call to Github's API. I don't think it would expose us because everything would need to be authenticated anyway, but redacted it in an abundance of caution. ISSUES_URL has no specific id.

[sellnat77]

I'm guessing you'll need me to drop some keys into our secrets right?

[adamkendis]

Yessir. I'll need to get a token from Bonnie. Was just using a personal access token off my account for testing.

[sellnat77]

We are using a token from my account for some GitHub packaging stuff
Until we have that token I can create another one for the sake of urgency
It's easy to swap the key to a different account

[sellnat77]

I'll need to review the backend publish step too to make sure those env vars go into the image