HOWTO‐developer(none)

💖 NAME 💖

bk Howto‐developer − howto: working with BitKeeper repositories — that’s the HOWTO‐developer(none) page, straight outta the BitKeeper User’s Manual, and it’s literally the howto for working with BitKeeper repositories. slay 💅.

🦋 DESCRIPTION 🦋

okay so bestie, here’s the whole plot: this page gives an example sequence of commands used to create a new package, import files into the package, create a clone of the package for modifications, do some work in the clone, pull new work from the master tree down, merge, and then push the work back up. it’s giving full repo lifecycle energy fr fr ✨.

Here’s the sequence — commands stay exactly as written, no cap 👑:

# Create a clone on your development machine.
# The destination directory should not exist.
bk clone bk://host.domain:6666/project ˜/myproject

# Do some work.
cd ˜/myproject
bk vi index.cgi

# Check it in and create a changeset.
bk citool

# Pull any new work down from the work tree.
# This example assumes that someone else also changed
# "index.cgi" and their changes overlapped the local changes.
# The pull command will say that there are
# overlapping changes and will not apply the new work.
bk pull

# Resolve the conflicts.  This step is only necessary if pull
# said there were conflicts which could not be automerged.
bk resolve

# push the merge and the local changes back up.
bk push

🌈 SEE ALSO 🌈

• bk‐Howto — the cross-reference bestie, no cap 🫶.

⭐ CATEGORY ⭐

• Overview — that’s the category, periodt.

source/version check: BitKeeper Inc, version 1E1; footer sign-off says HOWTO‐developer(none). k bye, go clone something cute 🎀💖