BST-WORKSPACE-OPEN(1)

💖 bst-workspace-open — open a new workspace, bestie 💖

okay so real quick, this is the manual page for bst-workspace-open, from the bst workspace open Manual, and honestly? it's giving "let me just grab your source code and vibe with it locally". stay with me, it's short and it slays. ✨

---

✨ SYNOPSIS ✨

bst workspace open [OPTIONS] ELEMENTS...

like, you pass some OPTIONS (optional, no pressure) and then ELEMENTS... which is literally required because a workspace with nothing in it is not the moment. 💅

---

🌸 DESCRIPTION 🌸

Open a workspace for manual source modification.

that's it. that's the whole description. you're opening a workspace so you can manually mess with the source, no cap. sometimes you just gotta edit the files yourself and the tool needs to know about it. iconic behavior. 🎀

---

👑 OPTIONS 👑

• --no-checkout — do not check out the source, just link to the given directory instead. lowkey the "I already have it, don't touch it" energy. 🦋
• -f, --force — the workspace gets created anyway, even if the directory you're creating it in isn't empty or even if a workspace for that element already exists. forceful. main character. use with intention bestie. 🔥
• --directory DIRECTORY — only for when you give a single Element: sets the directory used to create the workspace. one element, one directory, very demure. 🎀
• --source-remote REMOTE — a remote for downloading cached sources. that's the plug for your sources, fr fr. ⭐
• --ignore-project-source-remotes — ignore remote source cache servers that the projects recommend. not me ignoring the recommendations 🙈 your call though.

---

heads up bestie: --directory is only for the single-Element situation, and -f / --force is the one that bulldozes past a non-empty directory or an existing workspace. know before you go. 💜

---

and that's the whole page, no crumbs left. written by the bst workspace open crew, version 2.5, dated 2025-05-09 — ty for coming to my ted talk, now go open that workspace. mwah. 💖🌈✨🫶