Closed twosavoie closed 7 months ago
Hello @twosavoie,
In our workspace settings we have a 'Prevent leaving workspace' toggle that owners can enable, which seems to have been enabled by the owner of this environment.
We'd recommend contacting them directly to ask them to toggle this off.
Hi, thanks for getting back to me so quickly!
I've checked the settings on the owner's account for the sandbox itself and Permissions and the "Prevent Leaving Workspace" option hasn't been toggled on. (see below) Is there a different place I should look?
Overnight I saw that clicking the word "Fork" created the error, but clicking the icon to the right of "Fork" and then the username in the dropdown allowed the sandbox to be forked.
Thanks again for your help.
Hello @twosavoie
I've just tested now and the forking seems to be working again. Are you still seeing the error?
Works perfectly - thanks so much for your help!
🐛 bug report
Preflight Checklist
Description of the problem
Update: a sandbox can be forked by clicking the icon next to "Fork" and then choose a username. I feel like that's a small target to hit. And a person would expect that clicking "Fork" would fork the repo.
I am unable to fork a sandbox that I don't own. I am able to fork my own sandboxs. When I try to fork, I receive a 401 error. "Forking Failed (401) You don't have the needed authorization for this workspace (skillcrush-curriculum)"
Before this, I was able to fork without issue.
Thanks for your help!
How has this issue affected you? What are you trying to accomplish?
I'm trying to fork a sandbox to complete a lesson.
To Reproduce
Try to fork a sandbox you don't own.
Link to sandbox: [[link][https://codesandbox.io/p/sandbox/js-lesson05-challenge-01-starter-yso2m?file=%2Findex.html)]() (optional)
Your Environment