Skip to content

Commit a1ab97f

Browse files
zircotezircote
committed
ci: add issue templates and labels configuration
- Add 6 YAML issue form templates: spec-change, spec-bug, schema-issue, host-adapter, website, feature-request - Add config.yml disabling blank issues with discussions link - Add labels.yml with 27 project-specific labels covering spec, components, hosts, workflow, priority, and status
1 parent 2e4ceb0 commit a1ab97f

8 files changed

Lines changed: 558 additions & 0 deletions

File tree

‎.github/ISSUE_TEMPLATE/config.yml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
---
2+
blank_issues_enabled: false
3+
contact_links:
4+
- name: Discussions
5+
url: >-
6+
https://github.com/zircote/ccpkg/discussions
7+
about: >-
8+
Ask questions and discuss ideas before
9+
filing an issue

‎.github/ISSUE_TEMPLATE/feature-request.yml‎

Lines changed: 58 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,58 @@
1+
---
2+
name: Feature Request
3+
description: >-
4+
Suggest tooling, CLI, or ecosystem
5+
improvements
6+
labels: ["enhancement"]
7+
body:
8+
- type: markdown
9+
attributes:
10+
value: >
11+
Use this template for tooling, CLI,
12+
registry, or ecosystem feature requests.
13+
For specification changes, use the
14+
Specification Change template instead.
15+
- type: dropdown
16+
id: area
17+
attributes:
18+
label: Area
19+
description: >-
20+
Which area does this feature relate to?
21+
options:
22+
- CLI tooling (ccpkg)
23+
- Registry protocol
24+
- Package validation
25+
- Build/packaging pipeline
26+
- Developer experience
27+
- Other
28+
validations:
29+
required: true
30+
- type: textarea
31+
id: summary
32+
attributes:
33+
label: Summary
34+
description: >-
35+
Brief description of the feature.
36+
validations:
37+
required: true
38+
- type: textarea
39+
id: motivation
40+
attributes:
41+
label: Motivation
42+
description: >-
43+
What problem does this solve? What
44+
workflow does it improve?
45+
validations:
46+
required: true
47+
- type: textarea
48+
id: proposal
49+
attributes:
50+
label: Proposed Solution
51+
description: >-
52+
Describe how you envision this working.
53+
- type: textarea
54+
id: alternatives
55+
attributes:
56+
label: Alternatives Considered
57+
description: >-
58+
What other approaches were considered?

‎.github/ISSUE_TEMPLATE/host-adapter.yml‎

Lines changed: 67 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,67 @@
1+
---
2+
name: Host Adapter Request
3+
description: >-
4+
Request support for a new AI coding assistant
5+
or report a host adapter issue
6+
labels: ["host-adapter"]
7+
body:
8+
- type: markdown
9+
attributes:
10+
value: >
11+
Use this template for issues related to
12+
AI coding assistant host adapters, new
13+
host support, adapter mapping problems,
14+
or portability gaps.
15+
- type: dropdown
16+
id: request-type
17+
attributes:
18+
label: Request Type
19+
description: >-
20+
What kind of host adapter work is needed?
21+
options:
22+
- New host adapter
23+
- Fix existing adapter mapping
24+
- Missing component type support
25+
- Hook event mapping issue
26+
- Instructions assembly issue
27+
- MCP/LSP integration gap
28+
validations:
29+
required: true
30+
- type: input
31+
id: host
32+
attributes:
33+
label: Host Application
34+
description: >-
35+
Which AI coding assistant does this
36+
relate to?
37+
placeholder: >-
38+
e.g., Claude Code, GitHub Copilot
39+
validations:
40+
required: true
41+
- type: textarea
42+
id: description
43+
attributes:
44+
label: Description
45+
description: >-
46+
Describe the adapter issue or new host
47+
request in detail.
48+
validations:
49+
required: true
50+
- type: textarea
51+
id: host-docs
52+
attributes:
53+
label: Host Documentation
54+
description: >-
55+
Links to the host application's
56+
extension/plugin documentation.
57+
- type: textarea
58+
id: mapping
59+
attributes:
60+
label: Component Mapping
61+
description: |
62+
For new hosts, describe how ccpkg
63+
components map to this host's
64+
extension system.
65+
For existing hosts, describe the
66+
specific mapping that is incorrect
67+
or missing.

‎.github/ISSUE_TEMPLATE/schema-issue.yml‎

Lines changed: 64 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,64 @@
1+
---
2+
name: Schema Issue
3+
description: >-
4+
Report a problem or propose a change to the
5+
manifest JSON Schema
6+
labels: ["schema"]
7+
body:
8+
- type: markdown
9+
attributes:
10+
value: >
11+
Use this template for issues specific to
12+
manifest.schema.json or other JSON Schema
13+
files.
14+
- type: dropdown
15+
id: issue-type
16+
attributes:
17+
label: Issue Type
18+
description: >-
19+
What kind of schema issue is this?
20+
options:
21+
- Schema validation too strict
22+
- Schema validation too permissive
23+
- Missing field or constraint
24+
- Schema does not match spec text
25+
- Schema syntax error
26+
- New field request
27+
validations:
28+
required: true
29+
- type: input
30+
id: schema-path
31+
attributes:
32+
label: Schema Path
33+
description: >-
34+
JSON path to the affected field.
35+
placeholder: >-
36+
e.g., $.properties.components
37+
validations:
38+
required: true
39+
- type: textarea
40+
id: description
41+
attributes:
42+
label: Description
43+
description: >-
44+
Describe the schema issue in detail.
45+
validations:
46+
required: true
47+
- type: textarea
48+
id: example
49+
attributes:
50+
label: Example Manifest
51+
description: >-
52+
Provide a manifest snippet that
53+
demonstrates the issue.
54+
render: json
55+
- type: textarea
56+
id: expected
57+
attributes:
58+
label: Expected Validation Result
59+
description: >-
60+
Should the example above pass or fail
61+
validation? What error message is
62+
expected?
63+
validations:
64+
required: true

‎.github/ISSUE_TEMPLATE/spec-bug.yml‎

Lines changed: 64 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,64 @@
1+
---
2+
name: Specification Bug
3+
description: >-
4+
Report an error, ambiguity, or contradiction
5+
in the specification
6+
labels: ["spec", "bug"]
7+
body:
8+
- type: markdown
9+
attributes:
10+
value: >
11+
Use this template to report problems in
12+
the specification text, schema, or
13+
examples.
14+
- type: dropdown
15+
id: bug-type
16+
attributes:
17+
label: Bug Type
18+
description: >-
19+
What kind of problem did you find?
20+
options:
21+
- Ambiguous language
22+
- Contradiction between sections
23+
- Incorrect example
24+
- Missing normative requirement
25+
- Schema does not match spec text
26+
- Broken cross-reference
27+
- Typo or formatting error
28+
validations:
29+
required: true
30+
- type: input
31+
id: spec-section
32+
attributes:
33+
label: Specification Section
34+
description: >-
35+
Which section contains the problem?
36+
placeholder: >-
37+
e.g., Section 3.2 - Manifest Schema
38+
validations:
39+
required: true
40+
- type: textarea
41+
id: description
42+
attributes:
43+
label: Description
44+
description: >-
45+
Describe the problem. Quote the relevant
46+
spec text if possible.
47+
validations:
48+
required: true
49+
- type: textarea
50+
id: expected
51+
attributes:
52+
label: Expected Behavior
53+
description: >-
54+
What should the specification say or how
55+
should it be interpreted?
56+
validations:
57+
required: true
58+
- type: textarea
59+
id: suggestion
60+
attributes:
61+
label: Suggested Fix
62+
description: >-
63+
If you have a proposed correction,
64+
describe it here.

‎.github/ISSUE_TEMPLATE/spec-change.yml‎

Lines changed: 99 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,99 @@
1+
---
2+
name: Specification Change
3+
description: >-
4+
Propose a change to the ccpkg specification
5+
labels: ["spec", "proposal"]
6+
body:
7+
- type: markdown
8+
attributes:
9+
value: >
10+
Use this template to propose additions,
11+
modifications, or removals to the ccpkg
12+
specification.
13+
- type: dropdown
14+
id: change-type
15+
attributes:
16+
label: Change Type
17+
description: >-
18+
What kind of specification change
19+
are you proposing?
20+
options:
21+
- New section or feature
22+
- Modification to existing section
23+
- Deprecation or removal
24+
- Clarification of ambiguous language
25+
validations:
26+
required: true
27+
- type: input
28+
id: spec-section
29+
attributes:
30+
label: Specification Section
31+
description: >-
32+
Which section(s) of the specification
33+
does this affect?
34+
placeholder: >-
35+
e.g., Section 4 - Component Types
36+
validations:
37+
required: true
38+
- type: textarea
39+
id: summary
40+
attributes:
41+
label: Summary
42+
description: >-
43+
Brief description of the proposed change.
44+
validations:
45+
required: true
46+
- type: textarea
47+
id: motivation
48+
attributes:
49+
label: Motivation
50+
description: >-
51+
Why is this change needed? What problem
52+
does it solve or what use case does it
53+
enable?
54+
validations:
55+
required: true
56+
- type: textarea
57+
id: proposal
58+
attributes:
59+
label: Proposed Change
60+
description: >-
61+
Describe the change in detail. Include
62+
proposed spec language where possible
63+
(using RFC 2119 keywords).
64+
validations:
65+
required: true
66+
- type: textarea
67+
id: alternatives
68+
attributes:
69+
label: Alternatives Considered
70+
description: >-
71+
What other approaches were considered
72+
and why were they rejected?
73+
- type: textarea
74+
id: impact
75+
attributes:
76+
label: Impact Assessment
77+
description: |
78+
Which areas does this change affect?
79+
- Manifest schema changes?
80+
- Host adapter changes?
81+
- Backward compatibility implications?
82+
- Tooling changes required?
83+
- type: dropdown
84+
id: hosts-affected
85+
attributes:
86+
label: Host Adapters Affected
87+
description: >-
88+
Which AI coding assistant adapters
89+
does this change affect?
90+
multiple: true
91+
options:
92+
- All hosts
93+
- Claude Code
94+
- GitHub Copilot
95+
- OpenAI Codex CLI
96+
- Google Gemini CLI
97+
- OpenCode
98+
validations:
99+
required: true

0 commit comments

Comments
 (0)