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
Repo selection steps in the cases of GitHub individual installation and Bitbucket project installation currently communicate to the DPU the set of selected repositories by updating the install_id (and we also update the repo_config table at the same time, deleting all the rows for repositories that are not selected.
This can create problems when a user already has setup once and comes back to the setup page, but only completes repository selection without re-running the docker. For example:
The setup API from the browser extension will not give accurate output
No webhook would be set up for the new repositories selected, so Vibinex will not work for them. Plus, since the install_id has been removed from the old repositories, so even if the webhook exists, it will not trigger the DPU to process the pull request.
Even manual triggers will stop working for the old repositories, for which the install_id has been deleted.
The text was updated successfully, but these errors were encountered:
Repo selection steps in the cases of GitHub individual installation and Bitbucket project installation currently communicate to the DPU the set of selected repositories by updating the
install_id
(and we also update therepo_config
table at the same time, deleting all the rows for repositories that are not selected.This can create problems when a user already has setup once and comes back to the setup page, but only completes repository selection without re-running the docker. For example:
install_id
has been removed from the old repositories, so even if the webhook exists, it will not trigger the DPU to process the pull request.install_id
has been deleted.The text was updated successfully, but these errors were encountered: