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
[feat] Enhanced RFC discussion integration with auto-sync
Improves RFC discussions with full proposal content, author info, and automatic synchronization when PRs are updated. Includes fork compatibility using pull_request_target workflows.
Key features:
- Rich discussion creation with embedded RFC content
- Auto-sync on PR updates via GraphQL mutations
- Better formatting and metadata display
- Maintains compatibility with fork contributions
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <[email protected]>
This is a test RFC to verify the enhanced discussion integration workflow. It includes automatic discussion creation with full proposal content and sync capabilities.
11
+
12
+
## Basic example
13
+
14
+
```javascript
15
+
// This is just test content to verify the workflow
16
+
console.log("Enhanced discussion workflow test");
17
+
```
18
+
19
+
## Motivation
20
+
21
+
We want to ensure that:
22
+
1. RFC discussions are created with full proposal content
23
+
2. Discussion content is automatically synced when PRs are updated
24
+
3. The workflow works correctly with forks
25
+
4. Users get a better experience with rich, formatted discussions
26
+
27
+
## Detailed design
28
+
29
+
The enhanced workflow includes:
30
+
31
+
-**Rich Discussion Creation**: Discussions now include the full RFC content, author information, and useful links
32
+
-**Automatic Sync**: When RFCs are updated via PR commits, the discussion content automatically updates
33
+
-**Better Formatting**: Discussions use proper markdown formatting with sections and metadata
34
+
-**Fork Compatibility**: Uses `pull_request_target` to work with fork contributions
35
+
36
+
### Technical Implementation
37
+
38
+
1. Enhanced creation workflow extracts RFC content from PR
39
+
2. Sync workflow monitors for PR updates and refreshes discussion content
40
+
3. GraphQL mutations update existing discussions
41
+
4. Proper permissions ensure fork compatibility
42
+
43
+
## Drawbacks
44
+
45
+
- Slightly more complex workflow configuration
46
+
- Requires GraphQL API usage for discussion updates
47
+
- May generate more GitHub API calls
48
+
49
+
## Alternatives
50
+
51
+
- Keep the simple discussion format
52
+
- Use manual discussion updates
53
+
- Rely on PR comments instead of discussions
54
+
55
+
## Adoption strategy
56
+
57
+
This is a workflow enhancement that doesn't affect end users directly. RFC authors will benefit from richer discussions automatically.
58
+
59
+
## Unresolved questions
60
+
61
+
- Should we add even more metadata to discussions?
62
+
- How should we handle very large RFC files?
63
+
- Should we include diff information in sync updates?
0 commit comments