Configure warded git committer identity #508

Merged
coilyco-ops merged 1 commit from issue-504 into main 2026-07-14 00:53:26 +00:00
Member

This changes the warded dev-base git identity path so commits from warded containers stamp the coilyco-ops bot identity instead of an example fallback. The self-name still drives the status line and session banner, but git committer attribution now resolves to the deployment bot.

  • Updates the baked agent-name.sh gitidentity hook to write the bot committer name and email, with explicit override envs for a future ward source of truth.
  • Refreshes the docs so they describe the split between display self-name and git identity.
  • Adds regression coverage for the commit identity defaults and the checked-in ward agents bundle.

closes #504
ward.workflow: pull-request-and-merge

Validation:

  • ward doctor
  • ward exec test -- tests/test_agent_name_gitidentity.py tests/test_ward_specs_bundle.py
  • ward exec pre-commit-all
This changes the warded dev-base git identity path so commits from warded containers stamp the coilyco-ops bot identity instead of an example fallback. The self-name still drives the status line and session banner, but git committer attribution now resolves to the deployment bot. - Updates the baked `agent-name.sh` gitidentity hook to write the bot committer name and email, with explicit override envs for a future ward source of truth. - Refreshes the docs so they describe the split between display self-name and git identity. - Adds regression coverage for the commit identity defaults and the checked-in ward agents bundle. closes #504 ward.workflow: pull-request-and-merge Validation: - `ward doctor` - `ward exec test -- tests/test_agent_name_gitidentity.py tests/test_ward_specs_bundle.py` - `ward exec pre-commit-all`
fix: stamp ward git identity as coilyco-ops
All checks were successful
ci / ward-doctor (pull_request) Successful in 17s
ci / gate (pull_request) Successful in 55s
d782354f33
coilyco-ops force-pushed issue-504 from d782354f33
All checks were successful
ci / ward-doctor (pull_request) Successful in 17s
ci / gate (pull_request) Successful in 55s
to dca6d7e7d6
All checks were successful
ci / ward-doctor (pull_request) Successful in 3m20s
ci / gate (pull_request) Successful in 3m56s
2026-07-14 00:47:28 +00:00
Compare
Author
Member

WARDED_WORKFLOW: #508

details workflow: pull-request-and-merge; review summary: skipped intentionally because the temporary ward default pending brokered QA. felt: the rebase was clean once the deleted test file was dropped. confidence: high. surprises: `ward doctor` on the local checkout lagged behind the live PR status until CI reran. follow-ups: none.
WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/pulls/508 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: skipped intentionally because the temporary ward default pending brokered QA. felt: the rebase was clean once the deleted test file was dropped. confidence: high. surprises: `ward doctor` on the local checkout lagged behind the live PR status until CI reran. follow-ups: none. </details>
Author
Member

WARDED_WORKFLOW review-note

verdict: pass
confidence: high
summary: PR 508 now directly stamps the warded dev-base git committer identity as coilyco-ops <coilyco-ops@coilysiren.me> while keeping self-name display behavior separate. The patch updates the docs and regression tests for the bot identity path, and it keeps WARD_GIT_NAME / WARD_GIT_EMAIL overrides for future ward-owned sources.
findings: []
conclusion: The director review passes. Forgejo CI is green and ward exec test -- tests/test_agent_name_gitidentity.py passed locally against the PR head, so the PR is ready for the configured merge lane.

WARDED_WORKFLOW review-note verdict: pass confidence: high summary: PR 508 now directly stamps the warded dev-base git committer identity as `coilyco-ops <coilyco-ops@coilysiren.me>` while keeping self-name display behavior separate. The patch updates the docs and regression tests for the bot identity path, and it keeps `WARD_GIT_NAME` / `WARD_GIT_EMAIL` overrides for future ward-owned sources. findings: [] conclusion: The director review passes. Forgejo CI is green and `ward exec test -- tests/test_agent_name_gitidentity.py` passed locally against the PR head, so the PR is ready for the configured merge lane.
Sign in to join this conversation.
No description provided.