yanoblog

(Now, if you’re like me, you’re only finding yourself commiting a file via the commandline because you’re working on a remote machine. Which probably means that you are taking part in a Bad Programming Practice, because Thou Shalt Always Test Locally And Only Then Release. But let’s set that aside. Sometimes, shit happens.)

If you are really like me, you probably made a change in an account named something like “mrbuild” or somesuch. IOW, not a real user. So before you commit files in that account, set BK_USER to your username, so the cset gets the correct name (and blame) and so the bk licensing doesn’t get confused.

Step 1. Figure out what’s changed.

bk sfiles -cp

If that looks right…

Step 2. Tell bitkeeper to add them to a changeset

bk sfiles -cp | bk ci -

(add comments as instructed)

Step 3. Commit the changes

bk commit

Step 4. Push the changes

bk push

(If you’ve been really bad and added a bunch of files in this account, you can run:

bk sfiles -x

to make sure the new files are what you expect, and then

bk sfiles -x | bk add -

Enjoy. And I hope you can learn to live with your shame.