BK-IGNORE(1)

💅 bk ignore — the manual, but make it make sense

okay so this is the page for bk ignore from the BitKeeper User's Manual, and bestie, it's literally just "tell BitKeeper what to not look at." Let's get into it 🫶

---

✨ NAME ✨

bk ignore — ignore shell glob patterns 💅

🌸 SYNOPSIS 🌸

bk ignore glob [glob ...]

🎀 DESCRIPTION 🎀

bk ignore tells BitKeeper to ignore the files you name when it's out there looking for extra files that are not under revision control. no cap.

This affects the output of bk gfiles -x and, like, every command that uses that output — so bk citool and bk extras too. it's giving "one flag to rule them all" energy 👑

Typical things to ignore are object files, core files, a.out, *.exe, and the like. the usual suspects, fr fr.

🦋 how the matching actually works (important!!)

• Patterns that do not contain a slash (/) character are matched against the basename of the file ✨
• Patterns that do contain a slash are matched against the pathname of the file, relative to the root of the repository 💜
• Using ./ at the start of a pattern means the pattern applies only to the repository root 🌈

⭐ the examples, slay

If you always want to ignore files named JUNK regardless of which directory they're in, you can say:

bk ignore JUNK

This matches JUNK and sub/dir/JUNK but not JUNK-PRECIOUS. iykyk 💀

If you want to match a file in just one subdirectory, you can do:

bk ignore sub/directory/this_one

which matches sub/directory/this_one but not other_dir/this_one. targeted. iconic. 🎯

If you want to ignore just the JUNK file at the root of the repository, you can do:

bk ignore ./JUNK

which matches JUNK but not sub/dir/JUNK. the ./ is doing the heavy lifting there, main character energy tbh 🫶

🌸 pruning, aka "don't even go there"

You can also prune certain subdirectories of your repository by appending -prune to the directory path; no BitKeeper operations will descend into that directory. literally blocked. 🙈

bk ignore 'sub/dir/build -prune'

⚠️ Note: it's important to use the quotes as shown when using -prune, because each command argument is treated as a separate pattern!! You may use -prune only with directory paths that are relative to the root of the repository. no exceptions bestie 😭

Pruning large non-revision-controlled directory trees that appear in your repository can significantly improve performance in some cases. so like... free speed. we love that for you 🔥

💜 no arguments? no problem

With no arguments, bk ignore shows the current ignore list. simple as that. ⭐

💅 where it lives

The ignore list is stored in the file BitKeeper/etc/ignore. You may edit this file if you wish; the format is simply one glob per line. Editing the ignore file is the only way to remove entries from the list. that's the whole vibe check — no bk unignore here, sorry 🧚

🍓 the default ignore list

PENDING -prune
BitKeeper/log -prune
BitKeeper/tmp -prune
BitKeeper/writer -prune
BitKeeper/readers -prune
BitKeeper/etc/level
BitKeeper/etc/csets-in
BitKeeper/etc/csets-out

🌈 the following additions are suggested

core
*.o
*.swp
*.a
*.exe
*~
*.rej
*.orig

like, just do it. your repo will thank you 💖

---

🔥 ADVANCED USAGE 🔥

You may manually add additional ignore patterns on a per user basis. ooooh, personalisation ✨

For example, if you have a tendency to have a file called "notes" that you never want to check in, and you also use .xxx as your junk files, then do this:

$ echo notes >> "`bk dotbk`/ignore"
$ echo '*.xxx' >> "`bk dotbk`/ignore"

obsessed. that's it, that's the tip 👑

---

🌟 SEE ALSO 🌟

bk-citool, bk-extras, bk-gfiles, bk-status — go read those too bestie, they're all linked 💜

---

👑 CATEGORY 👑

Admin ✨

---

and that's the whole page!! brought to you by BitKeeper Inc, version 1E1, for bk ignore(none). mwah 💋 stay globbing, bestie 🎀