You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Browse filesBrowse the repository at this point in the historyBrowse files
authored
Resolve PR 432 merge conflicts against current main (#434)
* Add GitHub Copilot provider support
* Address Copilot PR review feedback
* Address follow-up Copilot review feedback
* Resolve rebase conflicts on main
* Update apps/server/src/provider/Layers/CopilotAdapter.ts
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* Update apps/server/src/provider/Layers/CopilotAdapter.ts
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* Add PR review plan and improve action rail
Add PR_REVIEW_PLAN.md describing a phased plan to finish the PR review cockpit. Update PrReviewShell.tsx to enhance the action rail and expanded review panel: add formatting helpers for review decisions and conflict status, compute file stats, surface approval blockers and gating logic, show review decision with tone, file impact summary, and blocker/count UI, and restructure the expanded area into three info cards (Review decision, File impact, Approval status). Also adjust button layout and disable logic for Approve and minor spacing/styling tweaks.
---------
Co-authored-by: Jason <jasnsy@gmail.com>
Co-authored-by: Val Alexander <68980965+BunsDev@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Val Alexander <bunsthedev@gmail.com>
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
-[ ] Make it easier to see where maintainer attention is still needed.
31
+
-[ ] Verify selected-file behavior stays stable when data refreshes.
32
+
33
+
### 5. Blockers and workflow visibility
34
+
35
+
-[ ] Make mergeability, required checks, conflicts, and workflow blockers easier to understand from the page.
36
+
-[ ] Improve “why can’t I approve yet?” guidance.
37
+
-[ ] Ensure blocker state is visible without needing to hunt through inspector panels.
38
+
39
+
### 6. Maintainer workflow integration
40
+
41
+
-[ ] Confirm PR Review is fully discoverable through navigation and command palette.
42
+
-[ ] Identify any remaining maintainer entry points that should route into `/_chat/pr-review`.
43
+
-[ ] Avoid creating duplicate surfaces or split workflows.
44
+
45
+
## Phase 3 — End-to-end reliability
46
+
47
+
### 7. Validation and cleanup
48
+
49
+
-[ ] Run full validation for the changed slice, including typecheck if possible.
50
+
-[ ] Fix any lint/type/test issues introduced by the PR Review work.
51
+
-[ ] Keep scope tight and avoid unrelated file churn.
52
+
53
+
### 8. Real PR walkthrough
54
+
55
+
-[ ] Test the full maintainer flow against a real PR.
56
+
-[ ] Verify open review, inspect files, inspect threads, view recent maintainer reviews, submit review, and refresh behavior.
57
+
-[ ] Capture any UX or state-sync gaps found in real usage.
58
+
59
+
### 9. Final completeness pass
60
+
61
+
-[ ] Review the page as a whole for maintainer usability.
62
+
-[ ] Confirm the implementation feels like the canonical PR Review workflow, not a partial bolt-on.
63
+
-[ ] Produce a final summary of what is complete vs what is intentionally deferred.
64
+
65
+
## Execution order
66
+
67
+
1. Action rail polish
68
+
2. Review state clarity
69
+
3. Review history quality
70
+
4. File-level review signal
71
+
5. Blockers and workflow visibility
72
+
6. Maintainer workflow integration
73
+
7. Validation and cleanup
74
+
8. Real PR walkthrough
75
+
9. Final completeness pass
76
+
77
+
## Definition of done
78
+
79
+
- A maintainer can open `/_chat/pr-review`, understand PR state quickly, inspect review context, see recent maintainer activity, submit a review confidently, and trust the page to stay in sync afterward.
80
+
- The page is clearly the main PR review workflow in `okcode`.
81
+
- Validation is clean enough that we trust the implementation, not just the visuals.
0 commit comments