Skip to content

docs(changelog): record byte5ai engineering-standards bootstrap #32

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
iret77 wants to merge 1 commit into from
Closed

docs(changelog): record byte5ai engineering-standards bootstrap #32

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions docs/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,24 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

## [Unreleased]

### Added

- 2026-05-17 — byte5ai engineering-standards bootstrap (PR #31). Repo is now
on `status: applied` against `byte5ai/engineering-standards`:
- `.github/engineering-standards.yml` as the explicit marker.
- `.hooks/pre-push` blocks direct pushes to `main`/`master` locally.
- `script/setup` enables the hook and runs the npm bootstrap in one step.
- AGENTS.md gained a "Git Workflow & Engineering Standards" section.
- CONTRIBUTING.md documents the pre-push guard and forbids
`Co-Authored-By:` trailers for AI agents.
- Branch protection on `main` is enforced server-side: PR required,
force-push and deletion blocked, all four CI workflows (five contexts
including the `audit` matrix) wired up as required status checks.

GitHub Actions were disabled on the repo since 2026-05-11 and were
reactivated as part of this rollout. The follow-up CHANGELOG PR doubles
as the first end-to-end CI verification after reactivation.

### Changed

- `docs/CHANGELOG.md` reformatted to follow the Keep-a-Changelog convention.
Expand Down
Loading