convert-github-issue-to-discussion
Convert GitHub Issue to Discussion
Convert GitHub issues to discussions using browser automation when the gh CLI doesn't support this operation.
Prerequisites
agent-browserinstalled- User must log in to GitHub when prompted
Workflow
1. Open Browser in Headed Mode
agent-browser open "https://github.com/<owner>/<repo>/issues/<number>" --headed
The --headed flag shows the browser window so the user can log in.
2. Wait for User Login
Take a snapshot to check if logged in:
agent-browser snapshot -i
If you see "Sign in" in the elements, the user needs to log in. Let them know and wait for confirmation.
3. Navigate to the Issue
After login, go to the issue page:
agent-browser open "https://github.com/<owner>/<repo>/issues/<number>"
4. Find the Convert Button
Take a snapshot and look for "Convert to discussion":
agent-browser snapshot -i
Look for a button like:
- button "Convert to discussion" [ref=e137]
5. Click Convert to Discussion
agent-browser click @<ref>
6. Select Discussion Category
A dialog will appear with category options:
agent-browser snapshot -i
You'll see options like:
- combobox "Category for new discussion" [ref=e2]
- option "General" [ref=e3] [selected]
- option "Ideas" [ref=e4]
- option "Q&A" [ref=e6]
- button "I understand, convert this issue" [ref=e9]
Select appropriate category (Q&A for support questions, Ideas for feature requests):
agent-browser select @<combobox-ref> "Q&A"
7. Confirm Conversion
agent-browser click @<confirm-button-ref>
8. Verify Conversion
You don't need to verify, you are done now.
Quick Reference
# Open issue page with visible browser
agent-browser open "https://github.com/owner/repo/issues/123" --headed
# Wait for user to log in, then get elements
agent-browser snapshot -i
# Click convert button (ref from snapshot)
agent-browser click @e137
# Wait for dialog, get new elements
agent-browser wait 1000 && agent-browser snapshot -i
# Select category and confirm
agent-browser select @e2 "Q&A"
agent-browser click @e9
# Verify - should redirect to discussions
agent-browser wait 2000 && agent-browser get url
Category Guidelines
- Q&A: Support questions, debugging help, how-to questions
- Ideas: Feature requests needing discussion
- General: General conversation, announcements
- Show and tell: Project showcases
Cleanup
You do not have to close the browser, as we'll use the login state again to convert other issues to discussions
Looking for issues
When you are asked to find for more good issues to convert to discussions, use gh
More from freekmurze/dotfiles
php-guidelines-from-spatie
Describes PHP and Laravel guidelines provided by Spatie. These rules result in more maintainable, and readable code.
144context7-auto-research
Automatically fetches up-to-date documentation from Context7 when users ask about libraries, frameworks, APIs, or need code examples. Triggers proactively without explicit user request.
27react-native-best-practices
Provides React Native performance optimization guidelines for FPS, TTI, bundle size, memory leaks, re-renders, and animations. Applies to tasks involving Hermes optimization, JS thread blocking, bridge overhead, FlashList, native modules, or debugging jank and frame drops.
24agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
24copy-editing
When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' or 'copy sweep.' This skill provides a systematic approach to editing marketing copy through multiple focused passes.
24fix-github-issue
Fix GitHub issues using gh CLI. Use when asked to fix, resolve, or address a GitHub issue. Creates fixes on separate branches, runs tests locally, and creates PRs when tests pass. Requires gh CLI authenticated and repo cloned locally.
22