BK-LEVEL(1)

👑 bk-level(1) 👑

BitKeeper User’s Manual, bestie — and this page is all about giving your repo a level check. 💅

---

🌸 NAME 🌸

bk level — set or show the level of the repository. That’s the whole vibe. ✨

---

🦋 SYNOPSIS 🦋

bk level [−l] [num]

---

💖 DESCRIPTION 💖

Okay so bk level prints or sets the level of the repository. A repository with no level setting defaults to level 1. And when a repository is cloned, the level gets set automatically to the level of the parent repository — no cap, it just inherits the vibe. 🧬

With an argument, it sets the level to that argument. With no argument, the command prints the repository level. If an error occurs, the level is shown as 1 million (1000000). 😭 Like, that’s the “something went wrong” number, not a cute flex.

Repository levels may be used to control the flow of changesets. Changes may only flow to a repository of the same or higher level. The typical use for levels is to create a stable or bug-fix repository. If that repository has a lower level than the development repository, changes may be moved from stable to development, but not the other way. 🚦 Direction matters, bestie — stable can send stuff up to dev, not the reverse.

---

✨ OPTIONS ✨

• −l — just list the level on a line by itself. Useful for scripts. 🤖 Script girlies stay winning.

---

🎀 SEE ALSO 🎀

• bk‐clone
• bk‐pull
• bk‐push

Go check those out too, iykyk. 🫶

---

🌈 CATEGORY 🌈

Repository. Obviously. 💾👑

---

mwah 💋 this page is brought to you by the footer fam: BitKeeper Inc, version 1E1, footer tag bk level(none) — and that’s the whole sign-off, bestie. 🎀