Starting from the cloned folder, go up a directory, then run the project creation script. Your project is missing a bunch of critical files. json files), then deleted the whole workspace folder and cloned the repo, and now I'm stuck with the issues above. I tried a few things (including restoring the. This morning in VS Code I've lost the right-click SFDX commands on package.xml and the Authorize an Org command doesn't appear on the palette. json files which looked like VS Code config files - I may have accidentally removed them from my local folder. I didn't do any other activity in VS Code or the repo except for this initial commit. First I created a new project with manifest, retrieved some metadata, and then created the repo and pushed the files. I had created this repo using VS Code just a few days ago. Is it possible that I'm missing some VSCode config files in the repo?ĮDIT: Here's some background detail. I've searched around but haven't found a clear answer. If I create a new project with manifest, then the right-click commands appear for package.xml, but I can't clone into the workspace because git won't clone into an existing folder. Authorizing by CLI doesn't do anything - I still don't get the SFDX retrieve command when I right-click on the package.xml file.Ģ. If I clone the repo and then open the workspace in VS Code, I don't get the Authorize an Org command on the palette, even after waiting. I've read this question/answer but it doesn't work for me.ġ. What's the correct procedure to clone an existing repository and connect it to the sandbox? I'm using VS Code, Bitbucket, and a standard sandbox (not scratch org).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |