Skip to content

Prepare frontend to enable two different github integrations (legacy and new) #2938

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
themarolt opened this issue Mar 18, 2025 — with Linear · 0 comments
Open
Labels
Frontend 🖼️ Integrations Created by Linear-GitHub Sync

Comments

Copy link
Contributor

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.

@themarolt themarolt added Frontend 🖼️ Integrations Created by Linear-GitHub Sync labels Mar 18, 2025 — with Linear
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Frontend 🖼️ Integrations Created by Linear-GitHub Sync
Projects
None yet
Development

No branches or pull requests

1 participant