GitHub independence #263

New issue

Open

opened 2024-10-04 15:34:56 +00:00 by RaitoBezarius · 0 comments

RaitoBezarius commented

2024-10-04 15:34:56 +00:00

(Migrated from github.com)

This issue is not in the scope of our paid work and sprints.

Currently, we have GitHub dependencies in two forms:

OAuth 2 connector
Foreign entities who are allowed to perform actions (security team, etc.)

We can generalize the OAuth 2 connector properly without too much issue.
For foreign entities, we can move this problem to a generic userinfo request to analyze the roles and scopes which are bestowed upon someone.

We probably need to introduce some error handling to automatically disable some of the GitHub features if you are running with another forge.

At the same time, a trivial implementation would be the DevelopmentDirectory where we can make up whatever we want.

_This issue is not in the scope of our paid work and sprints._ Currently, we have GitHub dependencies in two forms: - OAuth 2 connector - Foreign entities who are allowed to perform actions (security team, etc.) We can generalize the OAuth 2 connector properly without too much issue. For foreign entities, we can move this problem to a generic userinfo request to analyze the roles and scopes which are bestowed upon someone. We probably need to introduce some error handling to automatically disable some of the GitHub features if you are running with another forge. At the same time, a trivial implementation would be the DevelopmentDirectory where we can make up whatever we want.