BK-REPOCHECK(1)

💖 bk repocheck — BitKeeper User’s Manual 💖

🌸 NAME 🌸

bk repocheck — check repository for consistency. Literally the repo vibe check, bestie.

✨ SYNOPSIS ✨

bk repocheck [−qS] [−−check_opts="options"]

🦋 DESCRIPTION 🦋

okay so bk repocheck is used to make sure that a repository is in a consistent state. It works in traditional standalone repositories as well as nested collections. No cap.

If you suspect there might be a problem with your repository, run bk repocheck. If you send email for support, please include the output of the following:

bk version
bk config
bk repocheck

This command is implemented on top of bk check. The default, when running a nested collection, is to run in parallel; in that case check output is suppressed unless there are errors. Highkey important, so you don’t get confused by the quiet.

---

💅 OPTIONS 💅

• −−check‐opts=opts — this long option may be used to pass any valid option to bk check. The format must include the leading − or −− for each option and each option must be separated by a space like so:

−−check−opts=’−fv −e’

• −q — run quietly.
• −S — just check the current repo. This has no effect in a traditional standalone repository, but in a nested collection, this will check just the current repository, not the entire nested collection.

🎀 SEE ALSO 🎀

bk‐check, bk‐support

👑 CATEGORY 👑

Repository

---

Sign-off: from BitKeeper Inc, version 1E1, on the dated bk repocheck(none) footer — byeee, bestie 🫶💅