BK-UNPULL(1)

πŸ“¦ version 7.3.3, in alpine 3.24

πŸ’… NAME πŸ’…

okay so bestie, this is bk unpull from the BitKeeper User’s Manual β€” manual name bk unpull(none) β€” and its whole vibe is undoing the changesets that got added by bk pull. iconic cleanup energy, no cap. 🧹✨

🌸 SYNOPSIS 🌸

bk unpull [βˆ’fqSs]

πŸ¦‹ DESCRIPTION πŸ¦‹

bk unpull removes the changesets that were added by the most recent bk pull command. literally the undo button for that pull, but make it Unix. πŸ˜­πŸ’–

If you’ve committed a local changeset, bk unpull can not be executed until that changeset is removed by bk undo. so yeah: local commit? handle it with bk undo first, bestie. 🫢

πŸŽ€ NOTE πŸŽ€

bk unpull will discard the merge changeset, if any β€” in this context that merge is not considered part of the local work. πŸ’€ If the merge was complicated, it is advisable to save a patch. consider this your gentle β€œsave first, panic later” moment. πŸ™ˆ

✨ OPTIONS ✨

  • βˆ’f β€” Force unpull. force it, bestie, with feeling. πŸ”₯
  • βˆ’q β€” Quiet mode. shhh, minimal output vibes. 🀫
  • βˆ’s β€” Do not save a backup patch in BitKeeper/tmp/unpull.patch. no backup patch, no extra file, just vibes. πŸŽ€

πŸ‘‘ SEE ALSO πŸ‘‘

  • bk‐pull
  • bk‐undo

🌈 CATEGORY 🌈

  • Common
  • Repository

🫢 sign-off time: source/version is BitKeeper Inc, version 1E1. The date slot in this footer is not listed, so there’s no date to report, bestie. Manual name: bk unpull(none). πŸ’–
πŸ“¦ where this page comes from
  • alpine 3.24: bitkeeper-doc 7.3.3-r1 Β· Apache-2.0
  • πŸ’– girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms