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
We have an organization config file for our developers hosted on Continue.dev. Recently we've needed to update it, however, when we try to access the link (continue.dev/{org-name}/{config} we get a 404 page not found error. On top of that, when we look for our Configurations in Organization Settings -> Configurations, none are listed. Including any new configurations. The new configurations do appear in the VS Code Extension.
One clue is that we need to update our GITHUB_PERSONAL_ACCESS_TOKEN in the Github MCP Server, but I don't understand why that would prevent us from seeing and editing configurations on continue.dev?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
We have an organization config file for our developers hosted on Continue.dev. Recently we've needed to update it, however, when we try to access the link (continue.dev/{org-name}/{config} we get a 404 page not found error. On top of that, when we look for our Configurations in Organization Settings -> Configurations, none are listed. Including any new configurations. The new configurations do appear in the VS Code Extension.
One clue is that we need to update our GITHUB_PERSONAL_ACCESS_TOKEN in the Github MCP Server, but I don't understand why that would prevent us from seeing and editing configurations on continue.dev?
Please advise.
Beta Was this translation helpful? Give feedback.
All reactions