BK-PENDING(1)

🦋 NAME 🦋

Okay bestie, say hi to bk pending — the command from the BitKeeper User’s Manual that lists deltas which need to be in a changeset. That’s the whole vibe: it’s the little list of “bestie, this still needs a changeset.” ✨

🌸 SYNOPSIS 🌸

bk pending [−S] [−q]

Lowkey the whole call is just that. Two optional flags, main character energy, no drama. 💅

🎀 DESCRIPTION 🎀

The bk pending command shows changes that have been checked into your local work area, but not yet committed to a changeset. You have to commit to a changeset in order to send the change to other work areas.

To see what needs to be committed to a change set, run:

$ bk pending

That’s it. It’s giving “what’s still sitting in my drafts folder?” but for changes. 🫶

✨ OPTIONS ✨

• −S, −−standalone — Limit the list to the current component. This has no effect in a traditional standalone repository, but in a nested collection, processes just the current component and not the entire nested collection. Component-level focus, no whole-nest chaos.
• −q — No output. Return 0 if there are pending files or 1 if there are not. Silent mode plus exit-code truth serum, iykyk.

📝 NOTE 📝

This command is roughly the same as

$ bk ‐e gfiles ‐pA | bk ‐P log ... ‐

or, in the presence of the −S option,

$ bk ‐R gfiles ‐pA | bk ‐R log ... ‐

“Roughly” is doing a lot of work there, but that’s what the page says — no extra lore from me. 😭

👀 SEE ALSO 👀

Go bother bk‐commit, bk‐changes, bk‐log, and bk‐gfiles — they’re all in the group chat. 💖

📂 CATEGORY 📂

Repository — that’s the category, periodt. 👑

---

Later, bestie 🫶 — signed by BitKeeper Inc, version 1E1. The footer doesn’t print a separate date, so I’m not inventing one, no cap. Stay iconic. 💖