gh-issue-kit 0.9.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,64 @@
1
+ name: Bug Report
2
+ description: File a bug report.
3
+ title: "[Bug]: "
4
+ labels: ["bug", "triage"]
5
+ projects: ["octo-org/1", "octo-org/44"]
6
+ assignees:
7
+ - octocat
8
+ body:
9
+ - type: markdown
10
+ attributes:
11
+ value: |
12
+ Thank you for helping us by filing a bug report.
13
+ - type: input
14
+ id: contact
15
+ attributes:
16
+ label: Summary
17
+ description: Please describe the bug briefly.
18
+ placeholder: 'Example: "A build error occurred"'
19
+ validations:
20
+ required: false
21
+ - type: textarea
22
+ id: what-happened
23
+ attributes:
24
+ label: Details
25
+ description: Also tell us what you expected to happen.
26
+ placeholder: Please describe what happened
27
+ value: "When I ran the `pnpm build` command, a build error occurred."
28
+ validations:
29
+ required: true
30
+ - type: dropdown
31
+ id: version
32
+ attributes:
33
+ label: Version
34
+ description: What version of our software are you running?
35
+ options:
36
+ - 1.0.2 (Default)
37
+ - 1.0.3 (Edge)
38
+ default: 0
39
+ validations:
40
+ required: true
41
+ - type: dropdown
42
+ id: browsers
43
+ attributes:
44
+ label: Browser where the issue occurred
45
+ multiple: true
46
+ options:
47
+ - Firefox
48
+ - Chrome
49
+ - Safari
50
+ - Microsoft Edge
51
+ - type: textarea
52
+ id: logs
53
+ attributes:
54
+ label: Relevant log output
55
+ description: If you have any relevant logs, please paste them here. They will be automatically formatted as code, so backticks are not needed.
56
+ render: shell
57
+ - type: checkboxes
58
+ id: terms
59
+ attributes:
60
+ label: Code of Conduct
61
+ description: By submitting this issue, you agree to follow our [Code of Conduct](https://example.com).
62
+ options:
63
+ - label: I agree to follow this project's Code of Conduct
64
+ required: true
@@ -0,0 +1,53 @@
1
+ name: Feature Request
2
+ description: |
3
+ Create an Issue to suggest a new feature or improvement. Include the
4
+ background, use case, and alternatives if you have considered any.
5
+ title: "[FEATURE] "
6
+ labels: [enhancement]
7
+ assignees: []
8
+ body:
9
+ - type: markdown
10
+ attributes:
11
+ value: |
12
+ Thank you for suggesting an improvement. Tell us what problem you want to solve and how this feature would help.
13
+ - type: input
14
+ id: summary
15
+ attributes:
16
+ label: Summary
17
+ description: Write a concise one-line summary of the requested feature.
18
+ placeholder: |
19
+ Example: "Add a CLI option to skip prompts"
20
+ validations:
21
+ required: true
22
+ - type: textarea
23
+ id: motivation
24
+ attributes:
25
+ label: Background and user story
26
+ description: Describe the problem and why this feature is needed.
27
+ placeholder: |
28
+ As a user, I want to run the generator without prompts.
29
+ This would make it easier to use from CI.
30
+ - type: textarea
31
+ id: proposed
32
+ attributes:
33
+ label: Proposed solution
34
+ description: Describe the implementation or API changes you have in mind.
35
+ placeholder: |
36
+ Example: "Add -n/--name and -f/--framework options to the CLI"
37
+ - type: textarea
38
+ id: alternatives
39
+ attributes:
40
+ label: Alternatives considered
41
+ description: Briefly describe any other approaches you considered.
42
+ - type: input
43
+ id: impact
44
+ attributes:
45
+ label: Expected impact
46
+ description: Note anything that may be affected, such as compatibility, tests, or templates.
47
+ placeholder: |
48
+ Example: "Backward compatible. Adds options only"
49
+ - type: textarea
50
+ id: additional
51
+ attributes:
52
+ label: Additional context
53
+ description: Add related links, mockups, or notes if you have any.
@@ -0,0 +1,66 @@
1
+ name: バグ報告
2
+ description: バグ報告を作成します。
3
+ title: "[Bug]: "
4
+ labels: ["bug", "triage"]
5
+ projects: ["octo-org/1", "octo-org/44"]
6
+ assignees:
7
+ - octocat
8
+ body:
9
+ - type: markdown
10
+ attributes:
11
+ value: |
12
+ バグ報告にご協力いただきありがとうございます。
13
+ - type: input
14
+ id: contact
15
+ attributes:
16
+ label: 概要
17
+ description: バグの概要に記述してください。
18
+ placeholder: |
19
+ 例: "ビルドエラーが起こった"
20
+ validations:
21
+ required: false
22
+ - type: textarea
23
+ id: what-happened
24
+ attributes:
25
+ label: 詳細
26
+ description: あわせて、どうなることを期待していたかも教えてください。
27
+ placeholder: |
28
+ 発生した内容を記入してください
29
+ value: "pnpm build コマンドを実行したところ、ビルドエラーが発生しました。"
30
+ validations:
31
+ required: true
32
+ - type: dropdown
33
+ id: version
34
+ attributes:
35
+ label: バージョン
36
+ description: 利用中のソフトウェアのバージョンを選択してください。
37
+ options:
38
+ - 1.0.2 (Default)
39
+ - 1.0.3 (Edge)
40
+ default: 0
41
+ validations:
42
+ required: true
43
+ - type: dropdown
44
+ id: browsers
45
+ attributes:
46
+ label: 問題が発生したブラウザ
47
+ multiple: true
48
+ options:
49
+ - Firefox
50
+ - Chrome
51
+ - Safari
52
+ - Microsoft Edge
53
+ - type: textarea
54
+ id: logs
55
+ attributes:
56
+ label: 関連するログ出力
57
+ description: 関連するログがあれば貼り付けてください。自動でコード形式になるため、バッククォートは不要です。
58
+ render: shell
59
+ - type: checkboxes
60
+ id: terms
61
+ attributes:
62
+ label: 行動規範
63
+ description: この Issue を送信することで、[行動規範](https://example.com) に従うことに同意したものとみなされます。
64
+ options:
65
+ - label: このプロジェクトの行動規範に従うことに同意します
66
+ required: true
@@ -0,0 +1,53 @@
1
+ name: 機能要望
2
+ description: |
3
+ 新機能や改善案を提案するための Issue を作成します。背景、ユースケース、
4
+ 代替案があれば記載してください。
5
+ title: "[FEATURE] "
6
+ labels: [enhancement]
7
+ assignees: []
8
+ body:
9
+ - type: markdown
10
+ attributes:
11
+ value: |
12
+ 改善案の提案ありがとうございます。解決したい課題と、その機能がどのように役立つかを教えてください。
13
+ - type: input
14
+ id: summary
15
+ attributes:
16
+ label: 概要
17
+ description: 要望する機能を 1 行で簡潔に書いてください。
18
+ placeholder: |
19
+ 例: "プロンプトをスキップする CLI オプションを追加したい"
20
+ validations:
21
+ required: true
22
+ - type: textarea
23
+ id: motivation
24
+ attributes:
25
+ label: 背景とユーザーストーリー
26
+ description: どんな課題があり、なぜこの機能が必要なのかを書いてください。
27
+ placeholder: |
28
+ ユーザーとして、対話なしでジェネレーターを実行できるようにしたいです。
29
+ そうすることで CI から利用しやすくなります。
30
+ - type: textarea
31
+ id: proposed
32
+ attributes:
33
+ label: 提案する解決策
34
+ description: 想定している実装や API 変更があれば書いてください。
35
+ placeholder: |
36
+ 例: "CLI に -n/--name と -f/--framework オプションを追加する"
37
+ - type: textarea
38
+ id: alternatives
39
+ attributes:
40
+ label: 検討した代替案
41
+ description: ほかに検討した方法があれば簡単に書いてください。
42
+ - type: input
43
+ id: impact
44
+ attributes:
45
+ label: 想定される影響範囲
46
+ description: 後方互換性、テスト、テンプレートへの影響など、関係しそうな点を書いてください。
47
+ placeholder: |
48
+ 例: "後方互換あり。オプション追加のみ"
49
+ - type: textarea
50
+ id: additional
51
+ attributes:
52
+ label: 補足情報
53
+ description: 関連リンク、モック、補足メモなどがあれば記載してください。
package/package.json ADDED
@@ -0,0 +1,36 @@
1
+ {
2
+ "name": "gh-issue-kit",
3
+ "version": "0.9.0",
4
+ "description": "A command line tool for GitHub issues.",
5
+ "homepage": "https://github.com/ShionTerunaga/gh-issue#readme",
6
+ "bugs": {
7
+ "url": "https://github.com/ShionTerunaga/gh-issue/issues"
8
+ },
9
+ "license": "MIT",
10
+ "repository": {
11
+ "type": "git",
12
+ "url": "git+https://github.com/ShionTerunaga/gh-issue.git"
13
+ },
14
+ "bin": {
15
+ "gh-issue-kit": "./dist/index.mjs"
16
+ },
17
+ "files": [
18
+ "dist",
19
+ "README.md",
20
+ "LICENSE"
21
+ ],
22
+ "type": "module",
23
+ "main": "./dist/index.mjs",
24
+ "exports": "./dist/index.mjs",
25
+ "publishConfig": {
26
+ "access": "public",
27
+ "registry": "https://registry.npmjs.org/"
28
+ },
29
+ "dependencies": {
30
+ "commander": "^14.0.3",
31
+ "fast-glob": "^3.3.3"
32
+ },
33
+ "engines": {
34
+ "node": ">=20"
35
+ }
36
+ }