Jinemi/thermograph
4
0
Fork 0
Code Issues 2 Pull requests 4 Projects Releases Packages Wiki Activity Actions 2

branching: release now carries the required check #168

Merged
emi merged 1 commit from docs/release-check-closed into dev 2026-08-02 00:20:01 +00:00
Conversation 0 Commits 1 Files changed 1 +12 -8
emi commented 2026-08-02 00:19:20 +00:00
Owner
Copy link

.claude/BRANCHING.md said release deliberately has no required check. That stopped being true once the check was enabled, and a stale runbook is a correctness bug in a file agents read before dispatching work.

Closed in the order the file itself prescribes: pr-build.yml learned to fire on release (#165), #167 confirmed the gate context actually appeared on a real PR, and only then was the check required. The warning is preserved — it still governs a context rename or a new protected branch.

`.claude/BRANCHING.md` said `release` deliberately has no required check. That stopped being true once the check was enabled, and a stale runbook is a correctness bug in a file agents read before dispatching work. Closed in the order the file itself prescribes: `pr-build.yml` learned to fire on `release` (#165), #167 confirmed the gate context actually appeared on a real PR, and only then was the check required. The warning is preserved — it still governs a context rename or a new protected branch.
emi added 1 commit 2026-08-02 00:19:22 +00:00
branching: release now carries the required check
All checks were successful
PR build (required check) / changes (pull_request) Successful in 7s
Details
secrets-guard / encrypted (pull_request) Successful in 8s
Details
shell-lint / shellcheck (pull_request) Successful in 7s
Details
PR build (required check) / build-frontend (pull_request) Has been skipped
Details
PR build (required check) / build-backend (pull_request) Has been skipped
Details
PR build (required check) / validate-observability (pull_request) Has been skipped
Details
PR build (required check) / gate (pull_request) Successful in 2s
Details
14835af3d8 
Closed in the order this file prescribes: pr-build.yml learned to fire on
release, #167 confirmed the gate context actually appeared, and only then was
the check required. The warning stays — it still governs a context rename or a
new protected branch, and the failure mode it describes is a 405 with no cause.
emi merged commit 960c936d86 into dev 2026-08-02 00:20:00 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
  
Compat/Breaking

Breaking change that won't be backward compatible

  
Kind/Bug

Something is not working

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Security

This is security issue

  
Kind/Testing

Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Jinemi/thermograph#168
No description provided.
Delete branch "docs/release-check-closed"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?