diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index b99b885..0000000 --- a/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,86 +0,0 @@ -name: Bug report -description: Report a defect in Harness (unexpected behavior, crash, broken install, etc.) -title: "[bug] " -labels: ["bug", "needs-triage"] -assignees: - - revfactory -body: - - type: markdown - attributes: - value: | - Thanks for taking the time to file a bug report. - - Before submitting, please skim open issues to avoid duplicates. - - **Triage SLA:** we aim to label new issues within 48h and respond substantively within 72h on business days (see [CONTRIBUTING.md](../../CONTRIBUTING.md)). - - - type: input - id: claude-code-version - attributes: - label: Claude Code version - description: Output of `claude --version` (e.g. `2.3.1`) - placeholder: "2.x.y" - validations: - required: true - - - type: dropdown - id: experimental-flag - attributes: - label: Experimental Agent Teams flag state - description: Is `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1` set in the shell where you hit this bug? - options: - - "Yes, flag is set to 1" - - "No, flag is unset" - - "I don't know / N/A" - validations: - required: true - - - type: textarea - id: reproduction - attributes: - label: Reproduction steps - description: Minimal steps to reproduce. Commands, config, and inputs please. - placeholder: | - 1. `claude plugin marketplace add harness@harness` - 2. `export CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1` - 3. `claude "build a harness for ..."` - 4. observe ... - validations: - required: true - - - type: textarea - id: expected - attributes: - label: Expected behavior - description: What did you expect to happen? - validations: - required: true - - - type: textarea - id: actual - attributes: - label: Actual behavior - description: What actually happened? Include error messages / stack traces verbatim. - validations: - required: true - - - type: dropdown - id: os - attributes: - label: Operating system - options: - - "macOS" - - "Linux" - - "Windows (WSL)" - - "Windows (native)" - - "Other (describe below)" - validations: - required: true - - - type: textarea - id: context - attributes: - label: Additional context (optional) - description: Logs, screenshots, or anything else that might help. Redact anything sensitive. - validations: - required: false diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index cd34d2e..0000000 --- a/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1,8 +0,0 @@ -blank_issues_enabled: false -contact_links: - - name: GitHub Discussions — open-ended questions & RFCs - url: https://github.com/revfactory/harness/discussions - about: Prefer this for design discussions, ideas, "how should we think about X", and anything not yet actionable as an issue. - - name: Security disclosure (private) - url: mailto:robin.hwang@kakaocorp.com?subject=%5Bharness-security%5D - about: Report security issues privately. Acknowledgement within 7 days, patch target 30 days. diff --git a/.github/ISSUE_TEMPLATE/feature_request.yml b/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index ec2b397..0000000 --- a/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,62 +0,0 @@ -name: Feature request -description: Propose a new capability or enhancement for Harness -title: "[feat] " -labels: ["enhancement", "needs-discussion"] -body: - - type: markdown - attributes: - value: | - Thanks for the idea. Features take a bit of back-and-forth — please help us with the "why" before the "what". - - For anything RFC-sized (new pattern family, runtime support, breaking API), consider starting in [GitHub Discussions](https://github.com/revfactory/harness/discussions) first. - - - type: textarea - id: problem - attributes: - label: What problem does this solve? - description: Describe the user or engineering pain point. Concrete scenario preferred. - placeholder: | - When I scaffold a team for ___, I end up manually ___ because ___. - validations: - required: true - - - type: textarea - id: proposal - attributes: - label: Proposed solution - description: Your idea for fixing it. Sketch API / CLI / workflow if relevant. - validations: - required: true - - - type: textarea - id: alternatives - attributes: - label: Alternatives considered - description: What other approaches did you think about, and why did you not pick them? - validations: - required: false - - - type: dropdown - id: related-pattern - attributes: - label: Related team-architecture pattern (if any) - description: Which of the 6 built-in patterns is this most relevant to? - options: - - "Not pattern-specific" - - "Pipeline" - - "Fan-out / Fan-in" - - "Expert Pool" - - "Producer–Reviewer" - - "Supervisor" - - "Hierarchical Delegation" - - "A new pattern (please describe below)" - validations: - required: true - - - type: textarea - id: additional - attributes: - label: Additional context (optional) - description: Links, prior art, screenshots, anything else. - validations: - required: false diff --git a/.github/ISSUE_TEMPLATE/question.yml b/.github/ISSUE_TEMPLATE/question.yml deleted file mode 100644 index 664ffe0..0000000 --- a/.github/ISSUE_TEMPLATE/question.yml +++ /dev/null @@ -1,35 +0,0 @@ -name: Question -description: Ask a how-to or clarification question about Harness -title: "[question] " -labels: ["question", "needs-triage"] -body: - - type: markdown - attributes: - value: | - Questions are welcome. If your question is open-ended or invites discussion, [GitHub Discussions](https://github.com/revfactory/harness/discussions) is usually a better venue. - - We try to triage questions within 48h. - - - type: textarea - id: question - attributes: - label: Your question - description: What would you like to know? - validations: - required: true - - - type: textarea - id: tried - attributes: - label: What have you tried? - description: Commands run, docs read, related issues you've already found. - validations: - required: false - - - type: textarea - id: docs - attributes: - label: Related docs / links (optional) - description: Paste links to sections of the README, docs, or issues you've already read. - validations: - required: false diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index 17ad83f..0000000 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,58 +0,0 @@ - - -## Summary - - - -## Motivation - - - -- Closes # -- Related to # - -## Scope of change - - - -- [ ] Skill / meta-skill logic -- [ ] Agent template(s) -- [ ] Plugin manifest (`.claude-plugin/plugin.json`, `marketplace.json`) -- [ ] Documentation (`README.md`, `README_KO.md`, `README_JA.md`, `docs/`) -- [ ] `CHANGELOG.md` -- [ ] CI / GitHub Actions -- [ ] Tests -- [ ] Other (describe): - -## Tests - - - -- [ ] `npx markdownlint '**/*.md'` passes -- [ ] Manual repro of the change works as expected -- [ ] New unit / integration tests added (if applicable) -- [ ] N/A — explain below - -## CHANGELOG update - - - -- [ ] Yes — added to `CHANGELOG.md` -- [ ] No — this change is not user-visible (docs-only / internal refactor) - -## SemVer impact - - - -- [ ] **Patch** — bug fix, no API change (`fix:`) -- [ ] **Minor** — additive, backward-compatible (`feat:`) -- [ ] **Major** — breaking change (`feat!:` or `BREAKING CHANGE:` in commit footer) -- [ ] **None** — docs / chore / refactor / test - -## Additional notes - -