Copilot workspace/manifest files are written to an unrelated directory coincidentally named copilot.

[cristobalmackenzie]

Hi,

I was following the quickstart from the docs, and initialized an app with copilot init.

After completing the quickstart, I had trouble deleting the .workspace file and couldn't figure out why. I later found that the .workspace and manifest files where created in another directory next to the one I was on, that happens to be called copilot also but is unrelated.

Running myuser@/repos/example-directory $ copilot init created all copilot files in a previously existing /repos/copilot directory, instead of in /repos/example-directory/copilot.

The copilot cli seems perfectly able to find these files which end up in an unrelated folder, except for deleting them after running copilot app delete.

[huanjani]

Hi, @cristobalmackenzie!

Eek, sorry about that! Thanks for bringing this to our attention. We wanted to give users the flexibility to run commands from different places in their filesystems, but this is an unintended consequence. We will look into preventing cases of mistaken 🧑‍✈️ identity from happening again!