Skip to content

chore: harden .gitignore against secrets and local config - #2

Merged
JoshLuedeman merged 1 commit into
mainfrom
chore/harden-gitignore
Sep 17, 2026
Merged

JoshLuedeman merged 1 commit into
mainfrom
chore/harden-gitignore

Conversation

@JoshLuedeman

Copy link
Copy Markdown
Contributor

Part of the org-wide hygiene pass. Refs POps-Rox/.github#1

Why

A full-history scan found private keys, a Kubernetes kubeconfig with cluster credentials, and a Terraform state file committed across this organization. The root cause was not carelessness in one repo — it was that nothing was configured to stop it:

Pattern Repos not ignoring it (of 69)
kubeconfig 67
*.key / *.pem 67
id_rsa 68
.env 63

Three repos had no .gitignore at all.

What this adds

An identical baseline block in every repo covering: Kubernetes credentials, private keys/keystores, Terraform state and local workspace, .env files, cloud CLI credential caches, vendored dependencies, and OS noise.

.env.example / .env.*.example stay tracked via explicit negation.

Note

Push protection is now enabled org-wide, but it only blocks recognized secret patterns — it will not stop a kubeconfig or .tfstate. This is the complementary control.

Removing this material from history is a separate decision tracked in POps-Rox/.github#1.

Adds the org-wide baseline blocking kubeconfigs, private keys and
keystores, Terraform state, .env files, cloud CLI credential caches,
vendored dependencies and OS noise.

Coverage gap this closes (measured across all 69 repos):
  kubeconfig   not ignored in 67
  *.key/*.pem  not ignored in 67
  id_rsa       not ignored in 68
  .env         not ignored in 63

.env.example and .env.*.example remain tracked via negation.

Refs POps-Rox/.github#1

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 0543f12b-012b-495d-a226-87b651348071
@JoshLuedeman
JoshLuedeman merged commit b721e45 into main Sep 17, 2026
1 check passed
@JoshLuedeman
JoshLuedeman deleted the chore/harden-gitignore branch September 17, 2026 21:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant