Conversation
|
@kodiai plan: append one line 'fork apply smoke' to docs/smoke/xbmc-kodiai-write-flow.md |
| write: | ||
| enabled: true | ||
| allowPaths: | ||
| - docs/** |
There was a problem hiding this comment.
The allowPaths pattern docs/** will match any path starting with docs/, but it's worth confirming this is the intended behavior. If the intent is to only allow modifications within the docs directory and its subdirectories, this pattern is correct. However, if there are specific subdirectories within docs/ that should be excluded (e.g., docs/internal/ or sensitive documentation), those should be explicitly denied or this pattern should be more restrictive.
Kodiai Review SummaryMinor |
|
@kodiai apply: append one line 'fork apply smoke' to docs/smoke/xbmc-kodiai-write-flow.md |
kodiai responseDone. I've appended the line Plan: Files:
Steps: The file has been updated locally. Reply with |
kodiai responseOpened PR: #23 |
kodiai-write-output-key: kodiai-write-output:v1:inst-109141824:xbmc/kodiai:pr-22:comment-3882074909:keyword-apply deliveryId: ae884ae0-0703-11f1-91df-c2559c455428
There was a problem hiding this comment.
Pull request overview
Adds repo configuration and documentation updates to support a smoke validation of fork vs same-repo write-mode behavior in xbmc/kodiai.
Changes:
- Document the smoke-test baseline in the
xbmc/kodiaiwrite-flow guide. - Enable mention handling and write-mode in
.kodiai.yml, restricting writes viaallowPaths.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| docs/smoke/xbmc-kodiai-write-flow.md | Adds a baseline note for the fork smoke branch validation doc. |
| .kodiai.yml | Enables mention + write-mode and restricts write scope to docs/**. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| write: | ||
| enabled: true | ||
| allowPaths: | ||
| - docs/** |
There was a problem hiding this comment.
write.allowPaths is currently set to docs/**, which permits write-mode changes anywhere under docs/. For a smoke test, consider narrowing this to the minimal scope needed (e.g., docs/smoke/** or specific files) to reduce the blast radius if someone triggers @kodiai apply: unintentionally.
| - docs/** | |
| - docs/smoke/** |
| write: | ||
| enabled: true | ||
| allowPaths: |
There was a problem hiding this comment.
Enabling write.enabled: true on the default branch allows mention-driven commits to land automatically (within the allowPaths policy). If this PR is only meant for a temporary smoke validation, consider keeping write-mode disabled on main and enabling it only on the smoke branch/PR under test, or time-boxing/reverting it afterward to reduce ongoing operational/security exposure.
|
phase-29 feedback capture verification trigger |
|
phase-29 post-deploy feedback sync trigger |
|
phase-29 feedback sync trigger after startup |
|
phase-29 live log capture trigger |
Smoke PR for fork plan/apply fallback validation in xbmc/kodiai.