You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On frontend we need a separate way to connect github integrations alongside the old one.
The new just needs the owner/repo to connect it and we will do connection to nango on our backend so frontend implementation should be very simple.
It appears that they may already be a frontend component already prepared that was supposed to be used with Github archive integration which was later deprecated so we can probably just used and modify that one (just in code class/file name rename etc.). VUE_APP_IS_GITHUB_ARCHIVE_ENABLED is tied to this feature and github-archive is a folder name.
The only thing here I would do is add an env variable with user ids that can access this new
github integration so that we have sort of a feature flag here to disable this for most of the users. I think it's simpler to do it on the frontend and we just disable this after once we roll it out to all users.
The text was updated successfully, but these errors were encountered:
On frontend we need a separate way to connect github integrations alongside the old one.
The new just needs the
owner/repo
to connect it and we will do connection to nango on our backend so frontend implementation should be very simple.It appears that they may already be a frontend component already prepared that was supposed to be used with Github archive integration which was later deprecated so we can probably just used and modify that one (just in code class/file name rename etc.).
VUE_APP_IS_GITHUB_ARCHIVE_ENABLED
is tied to this feature andgithub-archive
is a folder name.The only thing here I would do is add an env variable with user ids that can access this new
github integration so that we have sort of a feature flag here to disable this for most of the users. I think it's simpler to do it on the frontend and we just disable this after once we roll it out to all users.
The text was updated successfully, but these errors were encountered: