Allow user to use own userid

[scooper4711]

While the "create an issue without needing a userid" thing is cool and all, I'd like to have the issues created under my own name.
This would allow for updates and just in general knowing what modules I've reported bugs against.

[Ethck]

Apologies for taking a while to get on this. I will look into it this weekend.

[scooper4711]

Any update?

[Ethck]

Oh, totally forgot that I said I'd look into it. What I will say is that in order to implement it we would have to allow the request to the server to also include some kind of authentication from the user (in this case you'd have to provide one of Github's Personal Access Tokens). It's definitely something that is doable, but I'm going to need to check in with our server guy about it. Additionally, I've been busy as of late with other modules but do plan on getting around to a rather large update to bug reporter soon(ish). Again, apologies for the delay.

[scooper4711]

Can't you just leverage API tokens? I assume that's what you're doing today, but with your own token.
https://github.com/settings/tokens
https://gitlab.com/-/profile/personal_access_tokens
I think if you just allow the user to specify their own tokens, then replace whatever token you're currently using with the user provided token, you'll be all set.
Oh, and of course, if the user doesn't provide a token, you default back to your current token.

[scooper4711]

I don't know C sharp, but I assume this is the line to update to use the user's personal access token if provided:

bug-reporter/FoundryVttBugReporterApi/ReportBugFunction.cs

Line 184 in 13767bc

var githubPat = Environment.GetEnvironmentVariable("GithubPAT");

and

bug-reporter/FoundryVttBugReporterApi/ReportBugFunction.cs

Line 118 in 13767bc

_httpClient.DefaultRequestHeaders.Add("PRIVATE-TOKEN", Environment.GetEnvironmentVariable("GitlabPAT"));

[Ethck]

Everything you've said is pretty much right on the nose, it will just take slightly more time to implement since I'm working on other modules right now. In theory it's a pretty small fix, but we (me and the other devs) still need to have a conversation about whether or not this is something that we want to implement because in theory there could be some unforeseen complications.