conduit-ui/issue 问题修复 & 功能扩展

解决BUG、新增功能、兼容多环境部署,快速响应你的开发需求

邮箱:yvsm@zunyunkeji.com | QQ:316430983 | 微信:yvsm316

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.

Sentinel Certified Latest Version MIT License Total Downloads

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 repo scope

Testing

composer test

Related Packages

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 我们能提供哪些服务?
定制开发 / 二次开发

基于 conduit-ui/issue 在你已有业务上做功能扩展、字段裁剪、UI 适配、与内部账号 / 权限 / 日志系统的深度对接。

BUG 修复 & 性能优化

线上偶发问题、内存泄漏、慢查询、并发异常等排查修复;针对高流量场景做缓存、队列、索引层面的调优。

项目外包 & 长期维护

承接完整的项目从需求 → 设计 → 开发 → 上线 → 长期运维;也可按月提供技术保姆服务。

yvsm@zunyunkeji.com QQ:316430983 微信:yvsm316 西安尊云信息科技 · 专注 PHP / Go / 分布式系统研发

统计信息

  • 总下载量: 3
  • 月度下载量: 0
  • 日度下载量: 0
  • 收藏数: 0
  • 点击次数: 21
  • 依赖项目数: 0
  • 推荐数: 0

GitHub 信息

  • Stars: 0
  • Watchers: 0
  • Forks: 0
  • 开发语言: PHP

其他信息

  • 授权协议: MIT
  • 更新时间: 2025-12-11