Development record
The private banned-names list (.abcd/.work.local/private-names.txt, the keyed store the pre-commit name guard checks) can only be filled by hand, entry by entry, so on a fresh install it starts empty and every commit warns that the guard checks nothing. abcd could propose its entries itself: review the repository, its history, its record and the person's other local material for the names that must never reach a committed file (private repositories, collaborators, clients, internal hosts and project code names), and offer them for the person to confirm. How to find such names well, and without leaking them while looking, is a state-of-the-art question (named-entity and PII detection, secret scanners, private-term mining), not one to answer from memory.
The private banned-names list (.abcd/.work.local/private-names.txt, the keyed store the pre-commit name guard checks) can only be filled by hand, entry by entry, so on a fresh install it starts empty and every commit warns that the guard checks nothing. abcd could propose its entries itself: review the repository, its history, its record and the person's other local material for the names that must never reach a committed file (private repositories, collaborators, clients, internal hosts and project code names), and offer them for the person to confirm. How to find such names well, and without leaking them while looking, is a state-of-the-art question (named-entity and PII detection, secret scanners, private-term mining), not one to answer from memory.
Frontmatter
| id | iss-2610241234397418 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610241234397418-the-private-banned-names-list-abcd-work.md
open on GitHub ↗ · commit history ↗