feat: implement the resolve endpoint

[iyad-f]

Summary

Type of change

• Bug fix (fixes an issue, non-breaking)
• New feature (adds functionality, non-breaking)
• Breaking change (alters existing behaviour/compatibility)
• Refactor (internal cleanup, no behaviour change)
• CI / dependency update
• Documentation update

Checklist

• Self-reviewed the changes and removed debug code or unrelated changes
• Tests pass, and I have manually tested the GitHub Action where applicable
• Documentation or changelog has been updated where necessary
• Complies with the AI Contribution Policy

[vmphase]

Do you expect it to send the authorization url when the /v1/link?repository_id= endpoint is triggered? I was planning to directly trigger the GitHub action to send the link depending on /v1/resolve?... response.

[iyad-f]

Do you expect it to send the authorization url when the /v1/link?repository_id= endpoint is triggered? I was planning to directly trigger the GitHub action to send the link depending on /v1/resolve?... response.

The resolve endpoint sends back a setup_url which the action can send as a comment for the linking process

[vmphase]

This should be removed. If ever being planned to be used on our Go-backend, it should be dynamically loaded from GitHub environmental variables (secrets), as we can't load any variables from .env dynamically in action.yml, but still want to avoid duplicating the same values.

[iyad-f]

yeah i mean technically a secrets manager would be used to load secrets.

[vmphase]

Replace it with dynamic loading and mark this solved.

[iyad-f]

Uhh actually the aud is anyway present in the jwt token under the aud field i believe so this aint really a secret, although we do have to do this secrets manager for stuff like postgres password and discord client secret etc.

[iyad-f]

Do you expect it to send the authorization url when the /v1/link?repository_id= endpoint is triggered? I was planning to directly trigger the GitHub action to send the link depending on /v1/resolve?... response.

The resolve endpoint sends back a setup_url which the action can send as a comment for the linking process

What is the /v1/link/ endpoint's purpose then?

there is no /v1/link, its just /link (public for users to click), and its purpose is basically to have the repo id and gh user id in the query parameters and hmac signature eventually and then we redirect the user to github oauth flow to prove their github identitiy and then in the callback we have do stuff and then redirect them back to the github oauth screen and handle its callback. Atleast this is what i though