Skip to content

docs: update code review docs to clarify fork PRs #4753

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
emilieschario merged 1 commit into from
Jan 2, 2026
Merged

docs: update code review docs to clarify fork PRs #4753

emilieschario merged 1 commit into from
Jan 2, 2026
+1 −0

Conversation

@emilieschario
Copy link
Contributor

@emilieschario emilieschario commented Jan 2, 2026 •
edited
Loading

Summary

Updated the code review documentation to clearly state that PRs from forks are not supported

@emilieschario
docs: update code review docs to clarify fork PR security limitation
bb258aa 
- Added clear note in Limitations section that PRs from forks are not supported
- Mentioned security concerns as the reason for this limitation
- Clarified that only same-repository branch PRs can be automatically reviewed
@changeset-bot
Copy link

changeset-bot bot commented Jan 2, 2026

⚠️ No Changeset found

Latest commit: bb258aa

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@kiloconnect
Copy link
Contributor

kiloconnect bot commented Jan 2, 2026

✅ No Issues Found

1 file reviewed | Confidence: 95% | Recommendation: Merge

Review Details

Files: apps/kilocode-docs/docs/advanced-usage/code-reviews.md

Change: Added a single line to the "Limitations and Guidance" section clarifying that PRs from forks are not supported due to security concerns.

Checked: Documentation accuracy, formatting consistency, markdown syntax

Notes:

  • The new bullet point follows the existing formatting pattern (bold key phrase followed by explanation)
  • The placement is logical within the limitations section
  • The wording is clear and actionable for users
  • No changeset is required for documentation-only changes per project guidelines

@emilieschario emilieschario self-assigned this Jan 2, 2026
@emilieschario emilieschario changed the title docs: update code review docs to clarify fork PR security limitation docs: update code review docs to clarify fork PRs Jan 2, 2026
lambertjosh
lambertjosh approved these changes Jan 2, 2026
View reviewed changes
Copy link
Contributor

@lambertjosh lambertjosh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM although I can't easily validate the fork support I haven't tried it personally. If you have, ship it~

@emilieschario emilieschario merged commit 894359c into main Jan 2, 2026
12 checks passed
@emilieschario emilieschario deleted the docs/update-code-review-fork-security branch January 2, 2026 19:50
@lambertjosh
Copy link
Contributor

lambertjosh commented Jan 2, 2026

Ah, missed automerge. Let me try a quick fork.

@emilieschario
Copy link
Contributor Author

emilieschario commented Jan 2, 2026

You're good. I'm sure here

@lambertjosh
Copy link
Contributor

lambertjosh commented Jan 2, 2026

@emilieschario - maybe this worked since I am a member then? #4756

@emilieschario emilieschario mentioned this pull request Jan 6, 2026
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@lambertjosh lambertjosh lambertjosh approved these changes

@kevinvandijk kevinvandijk Awaiting requested review from kevinvandijk

Assignees

@emilieschario emilieschario

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@emilieschario @lambertjosh