BK-RMGONE(1)

Hey bestie 💖 this is the bk rmgone(none) page from the BitKeeper User’s Manual, and it’s lowkey the cleanup-crew command you need to know about. It handles files whose keys are chilling in the gone file, and honestly? The way it just removes the warnings is iconic. Periodt.

💅 NAME 💅

bk rmgone — remove files having keys in the gone file

✨ SYNOPSIS ✨

bk rmgone [−nqS]

🌸 DESCRIPTION 🌸

Okay so the bk rmgone command removes the sfiles and any gfiles associated with the keys listed in the gone file. No cap, it’s giving “files, you are no longer invited to this repo” energy 💅

Sfiles may be removed and their keys added to the gone file with the gone command. So yeah, gone handles the key situation, and bk rmgone handles the actual file removal.

Here’s the tea: when the ChangeSet containing changes to the gone file is pushed/pulled from another repository, BitKeeper will issue warnings indicating that you have files matching things in the gone file. That’s the annoying little notification vibe 😭 The bk rmgone command may be used to remove the files in question and thus permanently stopping the warnings. So you clean up the files, and the warnings are done — permanently. Slay.

🎀 OPTIONS 🎀

• −n — Dry run. Just print out the files that would be removed. It’s giving “look, don’t touch” energy ✨
• −q — Run quietly. No extra chatter, just vibes 🤫
• −S, −−standalone — In a nested collection the bk rmgone command normally removes all sfiles marked as gone in all components. With this option only the current component is checked for gone sfiles. So it’s the “stay in your own lane, component” option 🫶

⚠️ WARNING ⚠️

🚨 This command cannot be undone. Like, fr fr — no takebacks, no undo button, no “wait bestie I changed my mind.” Double-check before you send it.

🔗 SEE ALSO 🔗

bk‐gone

🗂️ CATEGORY 🗂️

Repository

---

Catch you later, besties 🫶 — BitKeeper Inc, version 1E1, signing off. (No date in the footer, so we’re keeping it mysterious 🙈✨)