Commit orphaned per-branch session logs - #57
Merged
Conversation
The per-branch Stop hook attributes each turn to the branch checked out when it fires (end of turn), but committing a log is manual and tied to a feature branch's PR. Turns done on `main` (merges, issue/milestone triage) and post-merge wrap-up turns therefore landed in log files that no PR ever picked up, leaving them untracked in the working tree: - 2026-07-24-...-iss12-component-taxonomy.md - 2026-07-24-...-iss37-per-branch-session-logs.md - 2026-07-24-...-iss52-session-log-advisory.md - 2026-07-24-...-main.md These carry the prompts and responses behind several already-merged PRs (notably #53 and #54) plus administrative turns. Commit them unedited so the record is complete. The logs are auto-generated and committed as the hook wrote them — not hand-de-duplicated — even though the iss37 log overlaps heavily with the older cumulative-format log, because editing an auto-generated log by hand is how one got corrupted before. This is a point-in-time sweep; preventing recurrence is under discussion. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01R8QmvZEJTz9b7uNfJZTy3n
Contributor
Author
|
all clear, please merge. |
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01R8QmvZEJTz9b7uNfJZTy3n
goldingn
marked this pull request as ready for review
July 24, 2026 04:58
goldingn
added a commit
that referenced
this pull request
Jul 24, 2026
* Allow session-log-only commits to be pushed straight to main Every merge and admin turn on `main` appends to that branch's session log, which then has no PR to carry it — forcing a separate housekeeping PR each time (e.g. #57). A session-log commit is auto-generated provenance with nothing to review, so route it around the PR-only rule: - CLAUDE.md: carve out the one exception — commits touching nothing but `dev/sessions/` may be pushed directly to `main`. Stated where the rule is ("Branch & PR conventions", "Session logs", "Collaboration"). - README: match the transparency claim to reality — nothing that *changes the package* reaches `main` without review; the only direct-to-`main` commits are the logs themselves. - sweep-session-logs.sh: on the default branch, push the log commit after making it; on any other branch, leave it for that branch's PR. Branch protection cannot inspect commit contents, so enforcement is a maintainer bypass plus this convention — noted for #2, where protection is set up. Refs #2 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01R8QmvZEJTz9b7uNfJZTy3n * Add session log for the log-commits-to-main policy change Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01R8QmvZEJTz9b7uNfJZTy3n --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #56.
Commits four per-branch session logs that were left untracked in the working tree because the turns that produced them happened on
main(merges, triage) or as post-merge wrap-up, so no PR ever carried them. Between them they hold the prompts and responses behind several already-merged PRs (notably #53 and #54) plus administrative turns.main…-iss12-component-taxonomy.md…-iss52-session-log-advisory.md…-main.md…-iss37-per-branch-session-logs.mdCommitted unedited. I did not hand-de-duplicate the iss37 overlap: the logs are auto-generated, hand-editing them is how one got corrupted earlier in this project, and the redundancy is only against the superseded cumulative-format log. Completeness + not-touching-generated-files beats saving a few KB.
This PR is housekeeping only — a point-in-time sweep. Preventing recurrence is a workflow change I've put to the maintainer as a recommendation; it'll be its own issue/PR if we go ahead, and is deliberately out of scope here.
How this was produced