git-publish

To safely commit and push repository changes, stage only task-related files, run make build and make audit for site-affecting edits, honor pre-commit hook constraints, and use a semantic commit message before pushing to your branch.

When committing repo changes, avoid staging forbidden artifacts like .env, wip/, and _site/ directories, as pre-commit and pre-push hooks will block these paths to prevent broken or risky commits.

You need to run make build and make audit before a git push when your changes affect site content, configuration, layouts, includes, Sass, or assets, ensuring the publication workflow remains stable and review-ready.

Pre-commit hooks enforce staging discipline by blocking forbidden paths like .env and _site/, ensuring only relevant files are staged, which forces you to produce clean, scoped, imperative semantic commit messages suitable for history.

Yes, this git workflow supports Jekyll build validation by requiring make build and make audit checks to pass for site-affecting edits before finalizing your semantic commit and optionally pushing to the remote branch.

Git pushes fail when forbidden artifacts like .env, wip/, or _site/ are staged, because pre-commit and pre-push hooks block these paths to maintain staging discipline and prevent incomplete or risky repository updates.