Hi team,
we are on enterprise starter plan - we have added current repo (attached) in cody dashboard. but when we try to access the context in vscod
e, it says unavailable (attached)
okay here is n update - when i try to use the admin account i am able to link the current repo but it does not work with the users who we invited to.
the linked repo is of the user’s github personal account - and the user is not able to see.
admin can link the repo
Hey @hp-sewa
To be clear, you (as admin) can link the repo in the “Repository Manager” and have access to this repo in VS Code via “Remote Repository”?
But the team-mates don’t have access?
Are the team mates logged in to the same workspace instance?
Can they add a repository in the “Repository Manager” by themself?
Sorry for the inconvenience.
Yes, that is correct understanding and they are logged in as workspace.
The teammates do not see option to add repo - maybe because they are invited as regular user and not admin?
But are the team-mates able to look up context from the IDE for the repos you added as admin?
If, yes, then adding repositories as admin might be by design for security reasons. I’ll ask the dev team about that restriction.
If i promote the user to admin, the cody extension - still does not detect the current directory. it says not yet available.
i am not sure, if i am doing something wrong here - the org is a personal account - so maybe that can be an issue. Let me dig further, i will keep the thread posted.
i had to update the member to admin - link the github account and now it’s working.
Oh, that is great, but not ideal needing to raise the permissions for members to admins.
I have some other info for you.
If your repository is a private as org, your team members need to authorize the Code Bot to your private repository and you need to give them permission to do so.
Then they are able to connect to that repository.
Excerpt from the docs:
“… It’s important to note that members need to connect and authorize the code host (e.g., GitHub) to access these private repositories indexed in your Sourcegraph account. If this step is skipped, members won’t be able to access any of the private repositories they have permissions for.”
