Skip to content

chore: drop the mkdocs build output that was committed by mistake - #764

Merged
hokiepokedad2 merged 1 commit into
developfrom
fix/remove-mkdocs-build-output
Aug 20, 2026
Merged

chore: drop the mkdocs build output that was committed by mistake#764
hokiepokedad2 merged 1 commit into
developfrom
fix/remove-mkdocs-build-output

Conversation

@hokiepokedad2

Copy link
Copy Markdown
Contributor

My mistake in #763. I ran mkdocs build --strict to confirm the docs site still builds after the rewrite; that writes site/ beside docs/, and the git add -A in the same commit swept in 125 generated files and 12MB.

Nothing reads them — docs.yml runs mkdocs gh-deploy itself from docs/. Removed, and site/ is now in .gitignore so checking a docs build doesn't do this again.

No source or documentation content is touched.

https://claude.ai/code/session_01Nah4N2sGFs1TU2t7DXfKzJ

I ran `mkdocs build --strict` to check the docs site still builds, which writes
site/ next to docs/, and the commit in #763 swept 125 generated files and 12MB
into the repository. Nothing reads them: docs.yml runs mkdocs gh-deploy itself
from docs/.

Removed and added to .gitignore so the next person checking a docs build does
not repeat it.

Claude-Session: https://claude.ai/code/session_01Nah4N2sGFs1TU2t7DXfKzJ
@github-actions github-actions Bot added the fix label Aug 20, 2026
@hokiepokedad2
hokiepokedad2 merged commit a2e9f12 into develop Aug 20, 2026
5 checks passed
@hokiepokedad2
hokiepokedad2 deleted the fix/remove-mkdocs-build-output branch August 20, 2026 01:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant