brissue v2: research

[IzKuipers]

I need to figure out the best way to create issues from an external source. With the old brissue I created bug reports with the arcbugrep GitHub user (which still exists), but I know now that that wasn't the best method. I did it back then because it was the only way I knew. I need to figure out:

• the API endpoints on the ReArc side
• how GitHub bots work (this would be the best solution)
• how to assign tags, types and projects to an issue from ReArc
• What scopes would ultimately be assigned to this

[IzKuipers]

For the API endpoints:

• POST /admin/bughunt/brissue/:reportId -- Creates an issue for :reportId
• GET /admin/bughunt/brissue/:reportId -- Returns the issue associated with :reportId (if present)

The second one ultimately requires a database modification: I need to add BugReport.issueId which specifies the ID of the report's associated github issue.

[IzKuipers]

Secondly, instead of messing with GitHub bots, I'll just create the bug reports from a personal access token on my own account. This allows me to make use of Octokit for interfacing with GitHub, which is what I used before and what will ultimately make my life a whole lot easier.

[IzKuipers]

Regarding the tags and issue types, I do think that is built in to Octokit, though curiously it didn't work in brissue, probably because I fucked up the tag name.

[IzKuipers]

The admin scopes go as follows:

• admin.brissue.create -- Can create a github issue for a bug report
• admin.brissue.get -- Can view github issue status of a bug report

[IzKuipers]

@IzKuipers Continuing this for 7.0.10