Skip to content

docs(readme): add M-sec badges + untrack .vscode/#5

Merged
devonartis merged 1 commit into
developfrom
docs/readme-badges-gitignore
Apr 10, 2026
Merged

docs(readme): add M-sec badges + untrack .vscode/#5
devonartis merged 1 commit into
developfrom
docs/readme-badges-gitignore

Conversation

@devonartis

Copy link
Copy Markdown
Owner

Summary

Finishes Task 30 of the M-sec plan and closes the .vscode/ leak vector at the root.

README badges

Added three CI-health badges to README.md ahead of the public flip:

  • CIci.yml status on main
  • CodeQLcodeql.yml status on main
  • OpenSSF Scorecard — supply-chain posture

All three will render as "not found" or broken while the repo is private (CodeQL/Scorecard workflows are parked on workflow_dispatch: only per TD-VUL-006, and GitHub's Actions badges don't render without viewer auth on private repos). A README comment explains this and notes that the badges light up automatically when the repo flips public — fire-and-forget. No follow-up PR needed at public-flip time beyond the TD-VUL-005/006 workflow re-enable sequence.

The existing 8 static badges (pkg.go.dev, Go Report Card, License, Go Version, Docker, Security Policy, EdDSA, SPIFFE) are preserved.

.vscode/ fix

  • .vscode/settings.json was tracked on develop but carries per-user editor state (Snyk IDE prefs, etc.). git rm'd.
  • Added .vscode/ to .gitignore so VSCode can't recreate the file into a commit on any branch.
  • Closes the root cause of the leak caught during the first develop → main strip merge attempt, where VSCode recreated .vscode/settings.json between the strip and the merge commit and git add -A restaged it. The commit was amended (a72a959) to remove it before pushing, but the real fix is not having the file tracked in the first place. Done now.

CHANGELOG

Extended the Unreleased block with two new fix entries.

Local verification

  • go build ./cmd/broker ./cmd/aactl — OK
  • go test -short ./... — 15/15 packages PASS
  • golangci-lint run ./... — clean
  • ./scripts/test-gate-parity.sh — 13 gates match

PR checklist

README badges (Task 30 of M-sec plan):
  - CI (ci.yml status on main)
  - CodeQL (codeql.yml status on main)
  - OpenSSF Scorecard (supply-chain posture)

Added now, accepting that they'll be broken/not-found while the repo
is private. The moment the repo flips public (Phase 4 of release
strategy), they light up without needing a README update. CodeQL
and Scorecard will ALSO need their workflow triggers re-enabled per
TD-VUL-006 fix sequence — a README comment notes this.

The existing 8 static badges (pkg.go.dev, Go Report Card, License,
Go Version, Docker, Security Policy, EdDSA, SPIFFE) are preserved.

.vscode/ fix:
  - .vscode/settings.json was tracked on develop but carries per-user
    editor settings (Snyk IDE prefs, etc.). git rm'd from the tree.
  - Added .vscode/ to .gitignore so it can never land in any branch.
  - Root-causes the leak that happened during the first develop →
    main strip merge attempt: VSCode recreated the file between
    rm -rf and git commit, so it landed in the merge commit. The
    commit was amended (see a72a959), but the real fix is not having
    the file tracked in the first place. Done now.

Local verification:
  - go build ./cmd/broker ./cmd/aactl: OK
@devonartis devonartis merged commit 90aded2 into develop Apr 10, 2026
17 checks passed
@devonartis devonartis deleted the docs/readme-badges-gitignore branch April 10, 2026 12:59
devonartis added a commit that referenced this pull request Apr 10, 2026
Brings two documentation fixes from PR #5:
  - README badges: CI, CodeQL, OpenSSF Scorecard (will render broken
    while repo is private, auto-resolve on public flip)
  - .vscode/ removed from tree and added to .gitignore — closes the
    root cause of the settings.json leak caught during the previous
    develop → main strip merge

scripts/strip_for_main.sh ran clean in mid-merge mode (16 paths
checked, nothing to remove this round since a72a959 already handled
the dev file deletions). Build guard PASS.

Pre-commit hook (.githooks/pre-commit) also verified — no forbidden
paths in the staged changes.
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