joshtronic/igor
joshtronic/igor
Watch
2
Code Issues 3 Pull requests 2 Activity Actions

feat: maintain bot-owned repos (drop BOT_USER exclusion) #114

Merged
joshtronic merged 1 commit from feat/maintain-bot-owned-repos into master 2026-05-23 03:37:19 +00:00
Conversation 0 Commits 1 Files changed 1 +8 -9
joshtronic commented 2026-05-23 03:37:09 +00:00
Owner
Copy link

Brain, website, and the agent itself are first-class repos now --
they have real audit surface (npm deps on website, python deps on
agent) and security findings matter there too. Excluding them from
tier-2 maintenance was the wrong shape; the original "auditing your
own notes repo is busywork" rationale only holds for the brain.

Auto-detection in the maintenance prompt naturally no-ops on
markdown-only repos (no package.json, no requirements.txt, nothing
to audit). One wasted Claude call per week per such repo is an
acceptable cost compared to silently missing security findings on
the website or harness.

Co-Authored-By: Claude Opus 4.7 noreply@anthropic.com

Brain, website, and the agent itself are first-class repos now -- they have real audit surface (npm deps on website, python deps on agent) and security findings matter there too. Excluding them from tier-2 maintenance was the wrong shape; the original "auditing your own notes repo is busywork" rationale only holds for the brain. Auto-detection in the maintenance prompt naturally no-ops on markdown-only repos (no package.json, no requirements.txt, nothing to audit). One wasted Claude call per week per such repo is an acceptable cost compared to silently missing security findings on the website or harness. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
feat: maintain bot-owned repos (drop BOT_USER exclusion)
All checks were successful
Lint / check-sync (push) Successful in 5s
Details
Lint / check-sync (pull_request) Successful in 4s
Details
068b783979
 
Brain, website, and the agent itself are first-class repos now --
they have real audit surface (npm deps on website, python deps on
agent) and security findings matter there too. Excluding them from
tier-2 maintenance was the wrong shape; the original "auditing your
own notes repo is busywork" rationale only holds for the brain.

Auto-detection in the maintenance prompt naturally no-ops on
markdown-only repos (no package.json, no requirements.txt, nothing
to audit). One wasted Claude call per week per such repo is an
acceptable cost compared to silently missing security findings on
the website or harness.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
joshtronic deleted branch feat/maintain-bot-owned-repos 2026-05-23 03:37:20 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
Agent

   
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
Agent
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
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
joshtronic/igor!114
No description provided.