chore(repo): keep devops/ out of the public tree #74
Labels
No labels
NaNs
area/dsh
area/forgejo
experiment
priority/later
priority/next
priority/now
type/bug
type/task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
dsh-plugins/dsh-gitea#74
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The repo is public on git.pvlb.dev and push-mirrored to GitHub, and
devops/has been tracked since 2026-10-27 (9 commits). It is our internal runbook — deployment facts, host/profile paths, release and updater internals, security invariants — and it is not part of the open-source product. The operator asked to drop it from the public tree and gitignore it.Change
git rm -r --cached devops/and the rootinputsymlink; keep both on disk, operator-local..gitignore:devops/and/input.scripts/mirror-public.mjs: adddevops/toDEFAULT_EXCLUDES, so a sanitized snapshot can never pick it up again.AGENTS.md,assets/illustrations/README.md: stop pointing public files at a local-only path..forgejo/workflows/**stays tracked: CI cannot run from an ignored file, and the README no longer documents it (#73).Note for the operator
History still contains
devops/in the public commits since 2026-10-27, and the GitHub push mirror carries the same history. Untracking removes it from HEAD and from future snapshots, not from the past. A purge needs a history rewrite + force-push, which the house rule sanctions only with explicit operator approval (the 0.9.0 history compaction is the planned slot) — decision tracked in the session and to be confirmed.Acceptance
git ls-files devops→ empty; the files still exist on disk.git statusclean after the commit;npm run checkgreen.scripts/mirror-public.mjssnapshot contains nodevops/.devops/except historical CHANGELOG entries.