When I used the in-app feedback submission to create #81 it did so under Sully's account info
Assuming this is because some API call used their token, which is OK but I would strongly recommend configuring the call under some common non-user account, as simple as 'github-bot' or 'brain-bbqs-feedback'
This can help with both proper tracking and attribution from an analytics perspective
There are various mechanisms by which this can be done (I think the most formal/secure being an actual GitHub App), but usually something boils down to
git config --global user.name "[desired name of bot]"
git config --global user.email "github-bot@users.noreply.github.com"
regardless of whose API token happens to be used
OR -alternatively-
figure out some embedded GitHub Oauth and submit the feedback under the real user's account (cross-link the Globus with GitHub?)
When I used the in-app feedback submission to create #81 it did so under Sully's account info
Assuming this is because some API call used their token, which is OK but I would strongly recommend configuring the call under some common non-user account, as simple as 'github-bot' or 'brain-bbqs-feedback'
This can help with both proper tracking and attribution from an analytics perspective
There are various mechanisms by which this can be done (I think the most formal/secure being an actual GitHub App), but usually something boils down to
regardless of whose API token happens to be used
OR -alternatively-
figure out some embedded GitHub Oauth and submit the feedback under the real user's account (cross-link the Globus with GitHub?)