ahmza
91332d7e16
42c805f added the ignore rules ahead of running `git secret init`, which is
the right order - the rules should exist before any key material does. but
init was then never completed, so the repo has been sitting on a .gitsecret
containing nothing but a zero-byte paths/mapping.cfg: no keys directory, no
random_seed, no pubring, and no secrets ever registered.
nothing here is being encrypted and nothing is planned to be, so the rules
guard a workflow that does not exist. removing both halves rather than
leaving a half-initialised directory around, since the latter reads as "we
use git-secret" to anyone glancing at the tree.
the `!*.secret` negation goes with them. it only ever un-ignored the
encrypted blobs and never protected the plaintext originals, so it is not
load-bearing on its own.
nothing sensitive was present at any point, and nothing was committed.