diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md deleted file mode 100644 index ab92ff7..0000000 --- a/.github/ISSUE_TEMPLATE/bug_report.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -name: "Bug Report" -about: Report a technical issue encountered while using Labeled-CLI -title: "[BUG]: " -labels: bug -assignees: '' ---- - -## Contribution Checklist and Verification - -- [ ] I have searched the issue tracker and verified this issue does not already exist. (Exception: Automated system logs generated directly by Labeled-CLI running). -- [ ] My issue title strictly follows the format: `[BUG]: `. -- [ ] I understand that I must not start working on this until a maintainer assigns it to me via a comment request. - ---- - -### Current Behavior - - -### Expected Behavior - - -### Execution Context Details -- **Command Executed:** `labeled ` -- **Active Package Manager:** -- **Tested Environment:** -- **Labeled-CLI Version:** - -### Error Logs / Terminal Output - - -### Potential Suggestions / Fixes - diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml new file mode 100644 index 0000000..a997b10 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/bug_report.yml @@ -0,0 +1,74 @@ +name: '๐Ÿ› Bug Report' +description: 'File a structured bug report to help optimize the wrapper loop' +title: '[BUG]: ' +labels: ['bug'] +body: + - type: markdown + attributes: + value: | + ### Thanks for helping optimize labeled! + Please fill out this form accurately. Our automated pipeline uses these fields to spin up validation containers. + + - type: input + id: os_version + attributes: + label: 'Linux Distribution & Version' + description: 'Provide your specific OS details.' + placeholder: 'e.g., Fedora 40, Ubuntu 24.04 LTS, Arch Linux' + validations: + required: true + + - type: dropdown + id: manager_backend + attributes: + label: 'Active Package Manager' + description: 'Which system backend triggered the fault?' + options: + - 'apt' + - 'dnf' + - 'pacman' + - 'other / multiple' + validations: + required: true + + - type: input + id: cli_version + attributes: + label: 'Labeled Tool Version' + description: "Run 'labeled --version' in your terminal." + placeholder: 'e.g., 1.0.0' + validations: + required: true + + - type: textarea + id: reproduction + attributes: + label: 'Reproduction Commands' + description: 'What exact sequence of commands triggers the error?' + placeholder: | + 1. labeled install dev-env curl + 2. [Disconnect network] + 3. labeled remove dev-env + validations: + required: true + + - type: textarea + id: logs + attributes: + label: 'Terminal Error Output' + description: 'Paste raw error messages or state stack traces here.' + render: bash + + - type: checkboxes + id: guardrails + attributes: + label: 'Repository Guardrails' + options: + - label: 'I verify this is not an open security exploit report.' + required: true + - label: 'I have searched the issue tracker and verified this issue does not already exist. (Exception: Automated system logs generated directly by Labeled-CLI running).' + required: true + - label: 'My issue title strictly follows the format: `[BUG]: `.' + required: true + - label: 'I understand that I must not start working on this until a maintainer assigns it to me via a comment request.' + required: true diff --git a/.github/ISSUE_TEMPLATE/chore.md b/.github/ISSUE_TEMPLATE/chore.md deleted file mode 100644 index 5625f73..0000000 --- a/.github/ISSUE_TEMPLATE/chore.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -name: "Chore" -about: Routine repository maintenance, dependency updates, internal refactoring, or CI/CD updates -title: "[CHORE]: " -labels: chore -assignees: '' ---- - -## Contribution Checklist and Verification - -- [ ] I have verified this task does not duplicate a pending maintenance issue. -- [ ] My issue title strictly follows the format: `[CHORE]: `. -- [ ] I understand that I must not start working on this until a maintainer assigns it to me via a comment request. - ---- -### Description of Maintenance Task - - -### Rationale - - -### Targeted Files / Systems - - -### Verification Requirements - diff --git a/.github/ISSUE_TEMPLATE/chore.yml b/.github/ISSUE_TEMPLATE/chore.yml new file mode 100644 index 0000000..d25bee2 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/chore.yml @@ -0,0 +1,69 @@ +name: '๐Ÿงน Maintenance & Chore' +description: 'File a repository maintenance task, dependency bump, or CI/CD workflow update' +title: '[CHORE]: ' +labels: ['chore'] +body: + - type: markdown + attributes: + value: | + ### Repository Maintenance Entry + Use this form to map out structural refactors, build script adjustments, or automation pipeline updates. + + - type: dropdown + id: chore_category + attributes: + label: 'Chore Category' + description: 'Select the primary scope of this maintenance task.' + options: + - 'CI/CD Pipeline (.github/workflows)' + - 'Dependencies (package.json / lockfiles)' + - 'Build & Compilation System (build.js / tsconfig)' + - 'Repository Automation & Governance Templates' + - 'Other Maintenance' + validations: + required: true + + - type: input + id: target_files + attributes: + label: 'Target Files / Paths' + description: 'Which configuration or system files will this change affect?' + placeholder: 'e.g., package.json, eslint.config.js, .github/workflows/pr-pipeline.yml' + validations: + required: true + + - type: textarea + id: description + attributes: + label: 'Task Description' + description: 'Clearly state what needs to be updated and why this maintenance is necessary.' + placeholder: 'e.g., Upgrade Node.js environment to LTS version 22 across all action runner contexts to capture performance optimizations...' + validations: + required: true + + - type: textarea + id: outcome + attributes: + label: 'Technical Expected Outcomes' + description: 'What are the criteria for this chore to be considered complete?' + placeholder: | + - Pipeline executes successfully without environment errors. + - Dependency locks are deterministically updated. + validations: + required: true + + - type: checkboxes + id: verification + attributes: + label: 'Maintenance Guardrails' + options: + - label: 'I verify this is not an open security exploit report.' + required: true + - label: 'I have verified no other open issue is currently tracking this exact update.' + required: true + - label: 'My issue title strictly follows the format: `[CHORE]: `.' + required: true + - label: 'I understand that I must not start working on this until a maintainer assigns it to me via a comment request.' + required: true + - label: 'I confirm this work is strictly structural maintenance (no features, no core bug fixes).' + required: true diff --git a/.github/ISSUE_TEMPLATE/docs.md b/.github/ISSUE_TEMPLATE/docs.md deleted file mode 100644 index b8e64d0..0000000 --- a/.github/ISSUE_TEMPLATE/docs.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -name: "Documentation" -about: Improvements, fixes, or additions to the repository documentation and guides -title: "[DOCS]: " -labels: documentation -assignees: '' ---- - -## Contribution Checklist and Verification - -- [ ] I have verified this request does not duplicate a pending documentation issue. -- [ ] My issue title strictly follows the format: `[DOCS]: `. -- [ ] I understand that I must not start working on this until a maintainer assigns it to me via a comment request. - ---- -### Description of Documentation Changes - - -### Targeted Documentation Files - - -### Rationale - diff --git a/.github/ISSUE_TEMPLATE/docs.yml b/.github/ISSUE_TEMPLATE/docs.yml new file mode 100644 index 0000000..eb3cd07 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/docs.yml @@ -0,0 +1,71 @@ +name: '๐Ÿ“ Documentation Update' +description: 'File a request to improve, correct, or expand the documentation or wiki' +title: '[DOCS]: ' +labels: ['documentation'] +body: + - type: markdown + attributes: + value: | + ### Documentation Improvement Request + Use this form to flag outdated instructions, broken reference tables, typos, or clear gaps in our architecture guides. + + - type: dropdown + id: docs_scope + attributes: + label: 'Documentation Scope' + description: 'Which area of the project documentation needs adjustment?' + options: + - 'README / Main Landing Page' + - 'CONTRIBUTING Guide' + - 'SECURITY / License Layout Files' + - 'Wiki Architecture Pages' + - 'JSDoc / Codebase Inline Annotations' + - 'Other Documentation' + validations: + required: true + + - type: dropdown + id: priority_impact + attributes: + label: 'Impact Assessment' + description: 'How severely does this documentation issue affect users or developers?' + options: + - 'Critical (Broken setup commands, missing core requirements, broken links)' + - 'Standard Update (Expanding guides, updating configuration flags)' + - 'Typo / Style Fix (Fixing typos, grammar, or markdown spacing)' + validations: + required: true + + - type: textarea + id: problem_description + attributes: + label: 'Current Deficiency Description' + description: 'What is currently missing, misleading, or incorrect in the active documentation?' + placeholder: 'e.g., The setup step mentions using Node 18, but the modern ESLint 10 setup depends on flat configuration bindings requiring Node 20+...' + validations: + required: true + + - type: textarea + id: proposed_changes + attributes: + label: 'Proposed Text / Corrections' + description: 'Provide the updated phrasing or a clear layout outline of what should be written instead.' + placeholder: "Update Section 2 to state: 'Ensure your host local node execution runtime matches...' " + validations: + required: true + + - type: checkboxes + id: documentation_guardrails + attributes: + label: 'Documentation Guardrails' + options: + - label: 'I confirm that I have verified the accuracy of the proposed text changes.' + required: true + - label: 'I verify this is not an open security exploit report.' + required: true + - label: 'I have searched the issue tracker and verified this issue does not already exist. (Exception: Automated system logs generated directly by Labeled-CLI running).' + required: true + - label: 'My issue title strictly follows the format: `[DOCS]: `.' + required: true + - label: 'I understand that I must not start working on this until a maintainer assigns it to me via a comment request.' + required: true diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md deleted file mode 100644 index b60872c..0000000 --- a/.github/ISSUE_TEMPLATE/feature_request.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -name: "Feature Request" -about: Suggest a new feature, a schema change, or support for a new package manager -title: "[FEATURE]: " -labels: enhancement -assignees: '' ---- - -## Contribution Checklist and Verification - -- [ ] I have verified this request does not duplicate a pending request. (Exception: Issues submitted explicitly to expand support for adding new package managers). -- [ ] My issue title strictly follows the format: `[FEATURE]: `. -- [ ] I understand that before writing code, I must be assigned to this issue via a repository comment. - ---- -### Problem Statement - - -### Proposed Feature Solution - - -### Structural / Architecture Impact - - - - diff --git a/.github/ISSUE_TEMPLATE/feature_request.yml b/.github/ISSUE_TEMPLATE/feature_request.yml new file mode 100644 index 0000000..79fb1e8 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/feature_request.yml @@ -0,0 +1,68 @@ +name: '๐Ÿš€ Feature Request' +description: 'Propose a new utility capability, terminal flag, or engine behavior for labeled' +title: '[FEATURE]: ' +labels: ['enhancement'] +body: + - type: markdown + attributes: + value: | + ### Propose a New Extension + Thank you for suggesting an improvement! Please outline your idea clearly so we can evaluate its architectural alignment and hardware performance impact. + + - type: dropdown + id: feature_scope + attributes: + label: 'Feature Target Scope' + description: 'Which architectural layer does this feature target?' + options: + - 'Core Engine Logic (src/engine.ts)' + - 'CLI Argument / Flag Interface (src/index.ts)' + - 'Package Manager Integration (src/managers/*)' + - 'State & Storage Optimization (src/utils/saveData.ts)' + - 'Other System Extension' + validations: + required: true + + - type: textarea + id: user_problem + attributes: + label: 'Problem Statement / Use Case' + description: 'What limitation or friction in your current workflow does this feature solve? Describe clearly.' + placeholder: "e.g., Currently, when installing a tool chain that takes a long time, there's no way to pass an interactive timeout flag, causing background manager updates to hang silently on slower connections..." + validations: + required: true + + - type: textarea + id: proposed_implementation + attributes: + label: 'Proposed Solution & Terminal Behavior' + description: 'How should this feature work? Provide examples of the exact CLI commands, syntax variations, or expected tracking data structures.' + placeholder: | + Introduce a `--timeout ` flag that maps to execution spawn loops. + Example syntax: + labeled install dev-env curl --timeout 30 + validations: + required: true + + - type: textarea + id: technical_notes + attributes: + label: 'Architectural Implementation Ideas' + description: 'Optional notes on how this could be coded or which internal strategies are impacted.' + placeholder: 'This will require modifying the execution options structure in src/managers/index.ts to safely append custom abort signals...' + + - type: checkboxes + id: feature_guardrails + attributes: + label: 'Feature Proposal Alignment' + options: + - label: 'I confirm this proposal is a feature addition, not a bug report or structural maintenance task.' + required: true + - label: 'I verify this is not an open security exploit report.' + required: true + - label: 'I have verified that no other active issue or open discussion thread is tracking this exact proposal.' + required: true + - label: 'My issue title strictly follows the format: `[FEATURE]: `.' + required: true + - label: 'I understand that I must not start working on this until a maintainer assigns it to me via a comment request.' + required: true diff --git a/.github/ISSUE_TEMPLATE/performance.md b/.github/ISSUE_TEMPLATE/performance.md deleted file mode 100644 index 6f99dc2..0000000 --- a/.github/ISSUE_TEMPLATE/performance.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -name: "Performance" -about: Track and address execution speed, memory leaks, or storage bloat issues -title: "[PERF]: " -labels: performance -assignees: '' ---- - -## Contribution Checklist and Verification - -- [ ] I have searched the issue tracker and verified this issue does not already exist. -- [ ] My issue title strictly follows the format: `[PERF]: `. -- [ ] I understand that I must not start working on this until a maintainer assigns it to me via a comment request. - ---- -### Description of Performance Limitation - - -### Tested Environment and Hardware Context -- **Active Package Manager:** -- **OS / Distribution:** -- **Hardware Constraints:** - -### Metrics and Evidence - - -### Targeted Core Modules - - -### Proposed Optimization Approach - diff --git a/.github/ISSUE_TEMPLATE/performance.yml b/.github/ISSUE_TEMPLATE/performance.yml new file mode 100644 index 0000000..832f602 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/performance.yml @@ -0,0 +1,71 @@ +name: 'โšก Performance Optimization' +description: 'File an issue regarding execution delays, memory consumption, or tracking database bloat' +title: '[PERF]: ' +labels: ['performance'] +body: + - type: markdown + attributes: + value: | + ### Performance Optimization Log + Help us keep labeled lightning fast. Use this form to document execution friction, slow sub-process spawning, or excessive state-file disk reads. + + - type: dropdown + id: perf_category + attributes: + label: 'Bottleneck Category' + description: 'Where is the primary performance degradation occurring?' + options: + - 'Storage Data Bloat (tracking.json read/write cycles)' + - 'Execution Delay (Native shell package manager spawn loops)' + - 'Memory Safety & Resource Overhead' + - 'Build & Compilation Pipeline Latency' + - 'Other Performance Deficit' + validations: + required: true + + - type: dropdown + id: hardware_profile + attributes: + label: 'Hardware Environment Profile' + description: 'What type of system configuration is running this execution loop?' + options: + - 'Low-Spec Hardware (Resource-constrained CPU / Limited Memory)' + - 'Standard Development Laptop / Desktop Workstation' + - 'Remote Server / Cloud CI Runner Container' + validations: + required: true + + - type: textarea + id: measurement_data + attributes: + label: 'Observed Performance Metrics' + description: 'Provide quantitative data detailing the execution delays or resource usage.' + placeholder: | + - Current Execution Time: e.g., 'labeled list' takes 1.8 seconds to parse the tree. + - Expected Execution Time: Should complete instantly (under 150ms) via faster strategy index caching. + validations: + required: true + + - type: textarea + id: profiling_traces + attributes: + label: 'Profiling Traces / Benchmark Logs' + description: 'Paste raw data streams from benchmarks, console time executions, or memory profiles if available.' + render: text + placeholder: 'e.g., Output logs from execution benchmarking tool loops...' + + - type: checkboxes + id: performance_guardrails + attributes: + label: 'Performance Issue Alignment' + options: + - label: 'I verify that this issue specifically targets optimization improvements (not a regular bug or feature request).' + required: true + - label: 'I verify this is not an open security exploit report.' + required: true + - label: 'I have confirmed no other open tracking issue is actively addressing this specific code branch benchmark.' + required: true + - label: 'My issue title strictly follows the format: `[PERF]: `.' + required: true + - label: 'I understand that I must not start working on this until a maintainer assigns it to me via a comment request.' + required: true