-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy path.gfc.json
84 lines (84 loc) · 2.95 KB
/
.gfc.json
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
{
"templateLines": [
{
"description": "subject",
"lineFields": [
{
"name": "type",
"type": "select",
"startString": "",
"endString": "",
"question": "Commit type:",
"description": "",
"data": [
"fix",
"feat",
"build",
"ci",
"docs",
"perf",
"refactor",
"style",
"test"
]
},
{
"name": "scope",
"type": "text",
"startString": "(",
"endString": "):",
"question": "Scope:",
"description": "Scope of affected module.",
"data": [],
"minLength": 5,
"maxLength": 15
},
{
"name": "message",
"type": "text",
"startString": " ",
"endString": "",
"question": "Commit message:",
"description": "Message of commit",
"data": [],
"minLength": 5,
"maxLength": 85
}
]
},
{
"description": "body",
"startString": "\r\n\r\n",
"lineFields": [
{
"name": "description",
"type": "text",
"startString": "",
"endString": "",
"question": "Description:",
"description": "Just as in the subject, use the imperative, present tense: 'change' not 'changed' nor 'changes'.\nThe body should include the motivation for the change and contrast this with previous behavior.",
"data": []
}
]
},
{
"description": "footer",
"startString": "\r\n\r\n",
"lineFields": [
{
"name": "description",
"type": "text",
"startString": "",
"endString": "",
"question": "Footer:",
"description": "The footer should contain any information about Breaking Changes and is also the place to reference GitHub issues that this commit Closes. \nBreaking Changes should start with the word BREAKING CHANGE: with a space or two newlines. \nThe rest of the commit message is then used for this.",
"data": []
}
]
}
],
"options": {
"addStartStringWhenEmpty": false,
"addEndStringWhenEmpty": false
}
}