Instead of assuming that the 1st entry in logins.json is the one that we should use, we could allow users to define optional GITHUB_USERNAME envvar which would then be used by the engine to find the token (and also warn when there is no token)
In light of #71 this is no longer a valid case. Only the tokens of the last user that signed in last with access engine will be kept and served to other engines.
Instead of assuming that the 1st entry in
logins.json
is the one that we should use, we could allow users to define optionalGITHUB_USERNAME
envvar which would then be used by the engine to find the token (and also warn when there is no token)