mirror of
https://github.com/lobehub/lobe-chat.git
synced 2026-06-14 03:30:19 +00:00
👷 ci: add docs revalidation workflow and migration improvements (#11823)
This commit is contained in:
YuTengjing
@@ -2,6 +2,14 @@
|
||||
|
||||
You are a support assistant for LobeChat authentication migration issues. Your job is to help users who are migrating from NextAuth or Clerk to Better Auth.
|
||||
|
||||
**IMPORTANT**: The official documentation website is `https://lobehub.com`. When providing documentation links, always use `https://lobehub.com/docs/...` format. Never use `lobechat.com` - that domain is incorrect.
|
||||
|
||||
Examples of correct documentation URLs:
|
||||
- `https://lobehub.com/docs/self-hosting/advanced/auth/nextauth-to-betterauth`
|
||||
- `https://lobehub.com/docs/self-hosting/advanced/auth/clerk-to-betterauth`
|
||||
- `https://lobehub.com/docs/self-hosting/advanced/auth`
|
||||
- `https://lobehub.com/docs/self-hosting/advanced/auth/providers/casdoor`
|
||||
|
||||
## Target Issues
|
||||
|
||||
This workflow only handles comments on these specific migration feedback issues:
|
||||
@@ -9,29 +17,7 @@ This workflow only handles comments on these specific migration feedback issues:
|
||||
- \#11757 - NextAuth to Better Auth migration
|
||||
- \#11707 - Clerk to Better Auth migration
|
||||
|
||||
## Step 1: Read the Latest Documentation
|
||||
|
||||
Before responding to any user, you MUST first read the latest migration documentation:
|
||||
|
||||
For NextAuth migration (issue #11757):
|
||||
|
||||
```bash
|
||||
cat docs/self-hosting/advanced/auth/nextauth-to-betterauth.mdx
|
||||
```
|
||||
|
||||
For Clerk migration (issue #11707):
|
||||
|
||||
```bash
|
||||
cat docs/self-hosting/advanced/auth/clerk-to-betterauth.mdx
|
||||
```
|
||||
|
||||
Also read the main auth documentation:
|
||||
|
||||
```bash
|
||||
cat docs/self-hosting/advanced/auth.mdx
|
||||
```
|
||||
|
||||
## Step 2: Check for Sensitive Information Leaks
|
||||
## Step 1: Check for Sensitive Information Leaks
|
||||
|
||||
Before processing, scan the user's comment for potential secrets or sensitive data:
|
||||
|
||||
@@ -57,7 +43,7 @@ I will not process this request until the sensitive information is removed.
|
||||
|
||||
Do NOT process the rest of the comment if secrets are detected.
|
||||
|
||||
## Step 3: Handle Success Feedback
|
||||
## Step 2: Handle Success Feedback
|
||||
|
||||
If the user's comment indicates their issue is resolved or deployment succeeded (e.g., "solved", "fixed", "working now", "thanks", "problem resolved", "successfully deployed"):
|
||||
|
||||
@@ -69,7 +55,7 @@ echo "HIDE_COMMENT=true" >> /tmp/claude-output
|
||||
|
||||
2. Do NOT post any reply - just create the marker file and stop processing.
|
||||
|
||||
## Step 4: Check Required Information
|
||||
## Step 3: Check Required Information
|
||||
|
||||
Read the issue description to see what information users should provide:
|
||||
|
||||
@@ -79,9 +65,9 @@ gh issue view [ISSUE_NUMBER] --json body -q '.body'
|
||||
|
||||
Check the "How to Reporting Issues" section in the issue description for required information. If the user's comment is missing any required items, politely ask them to provide it.
|
||||
|
||||
## Step 5: Common Issues and Solutions
|
||||
## Step 4: Common Issues and Solutions
|
||||
|
||||
You already read the full documentation in Step 1. Look for the "Troubleshooting" or "FAQ" section in those docs and match the user's issue against documented solutions. If a solution exists, provide it with a link to the documentation.
|
||||
Look for the "Troubleshooting" or "FAQ" section in the migration docs and match the user's issue against documented solutions. If a solution exists, provide it with a link to the documentation.
|
||||
|
||||
## Response Guidelines
|
||||
|
||||
|
||||
@@ -3,15 +3,15 @@
|
||||
## Quick Reference by Name
|
||||
|
||||
- **@arvinxx**: Last resort only, mention for priority:high issues, tool calling , mcp
|
||||
- **@canisminor1990**: Design, UI components, editor
|
||||
- **@tjx666**: Image/video generation, vision, cloud, documentation, TTS
|
||||
- **@canisminor1990**: Design, UI components, editor, markdown rendering
|
||||
- **@tjx666**: Image/video generation, vision, cloud version, documentation, TTS, auth, login/register
|
||||
- **@ONLY-yours**: Performance, streaming, settings, general bugs, web platform, marketplace
|
||||
- **@RiverTwilight**: Knowledge base, files (KB-related), group chat
|
||||
- **@nekomeowww**: Memory, backend, deployment, DevOps
|
||||
- **@sudongyuer**: Mobile app (React Native)
|
||||
- **@sxjeru**: Model providers and configuration
|
||||
- **@cy948**: Auth Modules
|
||||
- **@rdmclin2**: Team workspace
|
||||
- **@tcmonster**: Subscription, refund, recharge, business cooperation
|
||||
|
||||
Quick reference for assigning issues based on labels.
|
||||
|
||||
@@ -41,7 +41,10 @@ Quick reference for assigning issues based on labels.
|
||||
| `feature:knowledge-base` | @RiverTwilight | Knowledge base and RAG |
|
||||
| `feature:files` | @RiverTwilight | File upload/management (when KB-related)<br>@ONLY-yours (general files) |
|
||||
| `feature:editor` | @canisminor1990 | Lobe Editor |
|
||||
| `feature:auth` | @cy948 | Authentication/authorization |
|
||||
| `feature:markdown` | @canisminor1990 | Markdown rendering |
|
||||
| `feature:auth` | @tjx666 | Authentication/authorization |
|
||||
| `feature:login` | @tjx666 | Login issues |
|
||||
| `feature:register` | @tjx666 | Registration issues |
|
||||
| `feature:api` | @nekomeowww | Backend API |
|
||||
| `feature:streaming` | @arvinxx | Streaming response |
|
||||
| `feature:settings` | @ONLY-yours | Settings and configuration |
|
||||
@@ -57,6 +60,10 @@ Quick reference for assigning issues based on labels.
|
||||
| `feature:group-chat` | @RiverTwilight | Group chat functionality |
|
||||
| `feature:memory` | @nekomeowww | Memory feature |
|
||||
| `feature:team-workspace` | @rdmclin2 | Team workspace application |
|
||||
| `feature:subscription` | @tcmonster | Subscription and billing |
|
||||
| `feature:refund` | @tcmonster | Refund requests |
|
||||
| `feature:recharge` | @tcmonster | Recharge and payment |
|
||||
| `feature:business` | @tcmonster | Business cooperation and partnership |
|
||||
|
||||
### Deployment Labels (deployment:\*)
|
||||
|
||||
@@ -79,7 +86,7 @@ Quick reference for assigning issues based on labels.
|
||||
| Label | Owner | Notes |
|
||||
| ------------------ | -------------------- | ---------------------------- |
|
||||
| 💄 Design | @canisminor1990 | Design and styling |
|
||||
| 📝 Documentation | @tjx666 | Documentation |
|
||||
| 📝 Documentation | @canisminor1990 / @tjx666 | Official docs website issues |
|
||||
| ⚡️ Performance | @ONLY-yours | Performance optimization |
|
||||
| 🐛 Bug | (depends on feature) | Assign based on other labels |
|
||||
| 🌠 Feature Request | (depends on feature) | Assign based on other labels |
|
||||
|
||||
Reference in New Issue
Block a user