| name | issue-maker |
| description | Create or update Pollinations GitHub issues when asked to track work, using current repository conventions. |
Issue Maker
- Use
pollinations/pollinations. Check related open and closed issues/PRs, including the latest discussion and close reason, before creating a duplicate or reviving obsolete work. - Describe the current problem or requested outcome with a short title and up to three concrete bullets. Link related work; use a checklist when an issue covers several steps. The project manager bot sets area, type and priority (
operations/github/project-manager.md); don't add labels for them. - Follow the user's assignee preferences. Otherwise use the team ownership table below, checking current repository context when uncertain. Root
AGENTS.mddefines app-submission states. - Return the issue link and a concise summary. Use Discord-compatible formatting when requested.
- Do not create or modify local files for issue-only work.
| Person | GitHub | Area |
|---|---|---|
| Thomas | voodoohop |
General, models, infrastructure |
| Joshua | eulervoid |
Pollen, backend, auth |
| Elliot | elliotetag |
Community, newsletter, UI |