BST-SOURCE-PUSH(1)

💖 BST SOURCE PUSH(1) 💖

okay bestie, welcome to bst source push — it lives in the bst source push manual and it's literally the glow-up your sources have been waiting for 🦋

---

✨ NAME ✨

bst-source-push — push the sources in a pipeline, like sending your babies off to the cloud 💅

---

🎀 SYNOPSIS 🎀

bst source push [OPTIONS] [ELEMENTS]...

---

🌸 DESCRIPTION 🌸

So the whole vibe here is: push the sources you need in order to build the pipeline. That's it. That's the gig. ✨

Not me explaining the element rules but okay, they matter:

• If you don't name any elements at all, it'll push the sources of the project's default targets. No default targets configured? Then it's giving everything — sources of all project elements get pushed. 😭
• If you run this command from inside a workspace directory, the default is to push the sources of the workspace element. Main character energy.
• By default it will only try to push sources for the elements you specified. No surprise extras, no cap.

Wanna control which sources get fetched? That's what --deps is for, and here's the menu:

• none: No dependencies, just the element itself
• run: Runtime dependencies, including the element itself
• build: Build time dependencies, excluding the element itself
• all: All dependencies

---

💅 OPTIONS 💅

• --except PATH — leave certain dependencies out of the push, like sorry not you 🚫
• -d, --deps [none|build|run|all] — which dependencies to push. [default: none] (yes, it's shy by default 🙈)
• --source-remote REMOTE — a remote for uploading sources, pick your destination bestie 📤
• --ignore-project-source-remotes — ignore the remote source cache servers that projects recommend. Do your own thing, iconic 👑

---

fr fr, keep those option names and values exactly as they are — the command is not gonna vibe with typos 💀

---

okay that's the whole page, you ate that 🍓💖 this was the bst source push manual, version 2.5, dated 2025-05-09 — sending you love and successful pushes, mwah 🎀✨🦋