conduit-ui/issue
Composer 安装命令:
composer require conduit-ui/issue
包简介
GitHub issue management for agents
README 文档
README
Stop manually triaging issues. Start automating the repetitive work that keeps your team from shipping.
Bulk label, assign, close, and route issues across repositories with clean PHP code. Built for teams managing hundreds of issues across multiple projects.
Installation
composer require conduit-ui/issue
Why This Exists
Your team creates 50+ issues per week. You're manually labeling bugs, assigning features to team members, and closing duplicates. This package gives you the tools to automate all of it.
Quick Start
use ConduitUI\Issue\Issue; // Find and update a single issue Issue::find('owner/repo', 123) ->addLabels(['bug', 'priority-high']) ->assignTo('username') ->save(); // Bulk operations across multiple issues Issue::query('owner/repo') ->state('open') ->label('needs-triage') ->get() ->each(fn($issue) => $issue ->removeLabels(['needs-triage']) ->addLabels(['triaged']) ->save() );
Core Features
Smart Labeling
// Add, remove, or replace labels in bulk Issue::find('owner/repo', 456) ->addLabels(['bug', 'urgent']) ->removeLabels(['question']) ->save();
Assignment & Routing
// Route issues to team members based on labels Issue::query('owner/repo') ->label('frontend') ->open() ->get() ->each(fn($issue) => $issue->assignTo('frontend-team'));
Bulk State Management
// Close stale issues automatically Issue::query('owner/repo') ->state('open') ->updatedBefore(now()->subMonths(6)) ->get() ->each(fn($issue) => $issue->close('Closing due to inactivity'));
Advanced Filtering
Issue::query('owner/repo') ->author('username') ->assignee('team-member') ->labels(['bug', 'priority-high']) ->since(now()->subWeek()) ->sort('created', 'desc') ->get();
Comment Management
// Add automated responses $issue = Issue::find('owner/repo', 789); $issue->comment('Thanks for reporting! Our team will investigate.'); // Get all comments $comments = $issue->comments();
Comment Reactions
use ConduitUI\Issue\Facades\Issue; // Add a reaction to a comment $reaction = Issue::createCommentReaction('owner', 'repo', $commentId, '+1'); // List all reactions on a comment $reactions = Issue::listCommentReactions('owner', 'repo', $commentId); // Filter reactions by type $thumbsUp = $reactions->filter(fn($r) => $r->isThumbsUp()); // Remove a reaction Issue::deleteCommentReaction('owner', 'repo', $commentId, $reactionId);
Available reaction types: +1, -1, laugh, confused, heart, hooray, rocket, eyes
Lock & Unlock
// Lock heated discussions $issue->lock('too heated'); // Unlock when ready $issue->unlock();
Usage Patterns
Static API (Quick Operations)
use ConduitUI\Issue\Issue; $issue = Issue::find('owner/repo', 123); $issues = Issue::query('owner/repo')->open()->get();
Instance API (Multiple Operations)
use ConduitUI\Issue\IssueManager; $manager = new IssueManager('owner/repo'); $issue = $manager->find(123); $issues = $manager->query()->open()->get();
Data Objects
All responses return strongly-typed DTOs:
$issue->id; // int $issue->number; // int $issue->title; // string $issue->state; // 'open' | 'closed' $issue->author; // User object $issue->assignees; // Collection of User objects $issue->labels; // Collection of Label objects $issue->createdAt; // Carbon instance $issue->updatedAt; // Carbon instance $issue->closedAt; // ?Carbon instance
Real-World Use Cases
Automated Triage Bot
// Label bugs automatically based on title keywords Issue::query('owner/repo') ->state('open') ->created('after', now()->subHour()) ->get() ->filter(fn($issue) => str_contains(strtolower($issue->title), 'bug')) ->each(fn($issue) => $issue->addLabels(['bug', 'needs-triage']));
Team Assignment
// Route issues to on-call team member $oncall = getOncallEngineer(); // Your function Issue::query('owner/repo') ->label('incident') ->open() ->get() ->each(fn($issue) => $issue->assignTo($oncall));
Stale Issue Cleanup
// Close issues with no activity for 90 days Issue::query('owner/repo') ->state('open') ->updatedBefore(now()->subDays(90)) ->get() ->each(function($issue) { $issue->comment('Closing due to inactivity. Please reopen if still relevant.'); $issue->close(); });
Configuration
Publish the config file:
php artisan vendor:publish --tag="issue-config"
Set your GitHub token in .env:
GITHUB_TOKEN=your-github-token
Requirements
- PHP 8.2+
- GitHub personal access token with
reposcope
Testing
composer test
Related Packages
- conduit-ui/pr - Pull request automation
- conduit-ui/repo - Repository governance
- conduit-ui/connector - GitHub API transport layer
Enterprise Support
Managing issues across 100+ repositories? Contact jordan@partridge.rocks for custom automation solutions.
License
MIT License. See LICENSE for details.
conduit-ui/issue 适用场景与选型建议
conduit-ui/issue 是一款 基于 PHP 开发的 Composer 扩展包,目前已累计 3 次下载、GitHub Stars 达 0, 最近一次更新时间为 2025 年 12 月 11 日, 在 PHP 生态内属于活跃度较高的组件。
它主要适用于以下技术方向: 「api」 「github」 「laravel」 「issues」 「saloon」 「conduit-ui」 等业务场景。在实际项目中,围绕这些方向常见需要落地的问题包括:接口对接、性能调优、并发安全、与既有框架(Laravel / ThinkPHP / Yii / Webman 等)的兼容适配,以及生产环境的日志埋点与稳定性保障。
我们在过去多个企业项目中使用过 conduit-ui/issue 或与其功能相近的方案,如果你在选型或落地过程中遇到问题,例如 版本兼容、二次改造、私有化封装、与内部系统对接、生产 BUG 排查,欢迎联系我们协助评估。
基于 conduit-ui/issue 在你已有业务上做功能扩展、字段裁剪、UI 适配、与内部账号 / 权限 / 日志系统的深度对接。
线上偶发问题、内存泄漏、慢查询、并发异常等排查修复;针对高流量场景做缓存、队列、索引层面的调优。
承接完整的项目从需求 → 设计 → 开发 → 上线 → 长期运维;也可按月提供技术保姆服务。
与 conduit-ui/issue 相关的其它包
同方向 / 同关键字的高下载量 PHP Composer 包推荐,方便对比选型:
Handles basic OAuth/OAuth2 authentication along with classes for common services
MediaWiki extension that allows embedding external content, specified by URL, into your wiki pages
A PSR-7 compatible library for making CRUD API endpoints
Laravel package for the simplification and integration of many of your users most wanted login providers. Installation is a breeze. Never worry about OAuth again.
GitHub Webhook Listener with plugin-based API for creating your own triggerered actions
Creates a markdown changelog for your GitHub repository.
统计信息
- 总下载量: 3
- 月度下载量: 0
- 日度下载量: 0
- 收藏数: 0
- 点击次数: 21
- 依赖项目数: 0
- 推荐数: 0
其他信息
- 授权协议: MIT
- 更新时间: 2025-12-11