ci: guard Kilo-only workflows in forks - #11210
Conversation
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Incremental Changes from Previous ReviewThe latest commit ("ci: trim fork workflow guards") addresses several previous review comments by removing
Guards were retained (or strengthened with
Other changes:
Files Reviewed (19 files + incremental)Carried forward from previous review:
New/changed since previous review:
Previous Review Summaries (2 snapshots, latest commit fadfa6f)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit fadfa6f)Status: No Issues Found | Recommendation: Merge Incremental Changes from Previous ReviewThe latest commit ("ci: trim fork workflow guards") addresses several previous review comments by removing
Guards were retained (or strengthened with
Other changes:
Files Reviewed (19 files + incremental)Carried forward from previous review:
New/changed since previous review:
Previous review (commit e1e2420)Status: No Issues Found | Recommendation: Merge This PR correctly adds A few notes on the implementation quality:
Files Reviewed (14 files)
Reviewed by gpt-5.6-sol · Input: 89.4K · Output: 9K · Cached: 386.6K Review guidance: REVIEW.md from base branch |
Local Review for branch diff:
|
2067c24 to
e1e2420
Compare
| jobs: | ||
| build: | ||
| name: Build docs site | ||
| if: github.repository == 'Kilo-Org/kilocode' # kilocode_change |
There was a problem hiding this comment.
i don't fully get it, why does this need to be disabled?
markijbema
left a comment
There was a problem hiding this comment.
Hey! Thanks for the PR: love that you picked it up broadly to make the contributor experience better.
However I stopped reviewing halfway because i think this is to overeager. I do agree it's a good idea to disable all jobs which are more infrastructural, but we dont need to disable jobs which are
- only manually invoked
- core test infrastructure (if this fails on forks we should look into that instead imho)
Can you please trim it down to only the infrastructure/autotriggered jobs?
|
Addressed the review feedback in fadfa6f: trimmed the fork repository guards down to infrastructure/autotriggered workflows, left manual-only and core test workflows runnable, and kept workflow_dispatch paths available on forks where applicable.\n\nValidation run locally:\n- bun run script/check-workflows.ts\n- bun run script/check-opencode-annotations.ts\n- git diff --check |
|
Hey @maphew, thanks for addressing the comments. Could you please resolve the conflict? |
b280aaa to
f225118
Compare
|
Thanks for improving this. Just merged. |
* ci: guard Kilo-only workflows in forks * ci: trim fork workflow guards --------- Co-authored-by: CI Bot <ci@beads.test>
Summary
Kilo-Org/kilocode.Why
Forks currently trigger workflows that require Kilo-owned infrastructure or credentials. Those jobs fail or queue indefinitely in forks, creating noisy and unactionable CI failures for fork owners.
Validation
bun run script/check-workflows.tsyq eval '.' .github/workflows/*.yml >/dev/nullgit diff --checkbun turbo typecheckgpt-5.5 on behalf of matt