You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> This is adapted from [Angular's commit convention](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-angular).
husky hooks are currently not compatible with GitHub Desktop's commit tool on Node 16+. There is an [open issue](https://github.com/desktop/desktop/issues/12562) about this on their repo, therefore there is nothing we can do about this. We recommend either committing through the command line, or using VSCode's source control.
16
+
17
+
### Examples
18
+
19
+
Appears under the "Features" header, `Command` subheader in a potential changelog:
20
+
21
+
```
22
+
feat(Command): add 'foo' command
23
+
```
24
+
25
+
Appears under the "Bug Fixes" header, `Database` subheader, with a link to issue #28 in a potential changelog:
26
+
27
+
```
28
+
fix(Database): handle caching
29
+
30
+
close #28
31
+
```
32
+
33
+
Appears under the "Performance Improvements" header, and under "Breaking Changes" with the breaking change explanation in a potential changelog:
34
+
35
+
```
36
+
perf(Server): improve patching by removing 'bar' option
37
+
38
+
BREAKING CHANGE: The 'bar' option has been removed.
39
+
```
40
+
41
+
The following commit and commit `667ecc1` do not appear in the changelog if they are under the same release. If not, the revert commit appears under the "Reverts" header.
42
+
43
+
```
44
+
revert: feat: Discussions (#4662)
45
+
46
+
This reverts commit c8cb81ec50aae940efa35ad3d69ee69c2db89125.
47
+
```
48
+
49
+
### Full Message Format
50
+
51
+
A commit message consists of a **header**, **body** and **footer**. The header has a **type**, **scope** and **subject**:
52
+
53
+
```
54
+
<type>(<scope>): <subject>
55
+
<BLANK LINE>
56
+
<body>
57
+
<BLANK LINE>
58
+
<footer>
59
+
```
60
+
61
+
The **header** and the **subject** are mandatory, while the **scope** of the header is optional.
62
+
63
+
### Revert
64
+
65
+
If the commit reverts a previous commit, it should begin with `revert:`, followed by the header of the reverted commit. In the body, it should say: `This reverts commit <hash>.`, where the hash is the SHA of the commit being reverted.
66
+
67
+
### Type
68
+
69
+
If the prefix is `feat`, `fix` or `perf`, it will appear in the changelog. However, if there is any [BREAKING CHANGE](#footer), the commit will always appear in the changelog.
70
+
71
+
Other prefixes are up to your discretion. Suggested prefixes are `chore`, `style`, `refactor`, and `test` for non-changelog related tasks.
72
+
73
+
### Scope
74
+
75
+
The scope could be anything specifying the place of the commit change, usually the name of a Presence. For example `Command`, `Database`, `SE` (syntax enforcer script), `Server` etc...
76
+
77
+
### Subject
78
+
79
+
The subject contains a succinct description of the change:
80
+
81
+
- use the imperative, present tense: "change" not "changed" nor "changes"
82
+
- don't capitalize the first letter
83
+
- no dot (.) at the end
84
+
85
+
### Body
86
+
87
+
Just as in the **subject**, use the imperative, present tense: "change" not "changed" nor "changes". The body should include the motivation for the change and contrast this with previous behavior.
88
+
89
+
### Footer
90
+
91
+
The footer should contain any information about **Breaking Changes** and is also the place to reference GitHub issues that this commit **Closes**.
92
+
93
+
**Breaking Changes** should start with the phrase `BREAKING CHANGE:` with a space or two newlines. The rest of the commit message is then used for this.
console.log(`${interaction.user.tag} used command ${interaction.commandName} in guild ${interaction.guild?.name} (${interaction.guild?.id}) in the channel ${interaction.guild?.channels.cache.get(interaction.channel?.idasstring)?.name} (${interaction.channel?.id})`);
22
+
}catch(error){
23
+
console.error(`Error while executing command ${interaction.commandName}: ${error}`);
24
+
awaitinteraction.reply({content: "There was an error while executing this command!",ephemeral: true});
console.log(`${interaction.user.tag} used command ${interaction.commandName} in guild ${interaction.guild?.name} (${interaction.guild?.id}) in the channel ${interaction.guild?.channels.cache.get(interaction.channel?.idasstring)?.name} (${interaction.channel?.id})`);
21
-
}catch(error){
22
-
console.error(`Error while executing command ${interaction.commandName}: ${error}`);
23
-
awaitinteraction.reply({content: "There was an error while executing this command!",ephemeral: true});
32
+
if(!interaction.guild)return;
24
33
34
+
try{
35
+
if(!command.autocomplete)return;
36
+
awaitcommand.autocomplete(interaction);
37
+
console.log(`${interaction.user.tag} autocompleted command ${interaction.commandName} in guild ${interaction.guild?.name} (${interaction.guild?.id}) in the channel ${interaction.guild?.channels.cache.get(interaction.channel?.idasstring)?.name} (${interaction.channel?.id})`);
38
+
}catch(error){
39
+
console.error(`Error while executing command ${interaction.commandName}: ${error}`);
0 commit comments