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
Copy file name to clipboardexpand all lines: .github/CONTRIBUTING.md
+22-22
Original file line number
Diff line number
Diff line change
@@ -2,39 +2,39 @@
2
2
3
3
**The issue tracker is only for bug reports and enhancement suggestions. If you have a question, please ask it in the [Discord server](https://discord.gg/djs) instead of opening an issue, or on [GitHub Discussions](https://github.com/discordjs/discord-api-types/discussions) – you will get redirected there anyway.**
4
4
5
-
-[Code of Conduct](https://github.com/discordjs/discord-api-types/blob/main/.github/CODE_OF_CONDUCT.md)
- Checkout a topic branch from a base branch, e.g. `main`, and merge back against that branch.
13
+
-Checkout a topic branch from a base branch, e.g. `main`, and merge back against that branch.
14
14
15
-
- If adding a new feature:
15
+
-If adding a new feature:
16
16
17
-
- Provide a convincing reason to add this feature. Ideally, you should open a suggestion issue first and have it approved before working on it.
17
+
- Provide a convincing reason to add this feature. Ideally, you should open a suggestion issue first and have it approved before working on it.
18
18
19
-
- If fixing a bug:
19
+
-If fixing a bug:
20
20
21
-
- If you are resolving a special issue, add `fix/close #xxxx[,#xxxx]` (#xxxx is the issue id) in your PR body for a better release log, e.g.
21
+
- If you are resolving a special issue, add `fix/close #xxxx[,#xxxx]` (#xxxx is the issue id) in your PR body for a better release log, e.g.
22
22
23
-
```
24
-
fix(Guild): handle events correctly
23
+
```
24
+
fix(Guild): handle events correctly
25
25
26
-
close #28
27
-
```
26
+
close #28
27
+
```
28
28
29
-
- Provide a detailed description of the bug in the PR. Live demo preferred.
29
+
- Provide a detailed description of the bug in the PR. Live demo preferred.
30
30
31
-
- It's OK to have multiple small commits as you work on the PR - GitHub can automatically squash them before merging.
31
+
- It's OK to have multiple small commits as you work on the PR - GitHub can automatically squash them before merging.
32
32
33
-
- Make sure tests pass!
33
+
- Make sure tests pass!
34
34
35
-
- Commit messages must follow the [commit message convention](./COMMIT_CONVENTION.md) so that changelogs can be automatically generated. Commit messages are automatically validated before commit (by invoking [Git Hooks](https://git-scm.com/docs/githooks) via [husky](https://github.com/typicode/husky)).
35
+
- Commit messages must follow the [commit message convention](./COMMIT_CONVENTION.md) so that changelogs can be automatically generated. Commit messages are automatically validated before commit (by invoking [Git Hooks](https://git-scm.com/docs/githooks) via [husky](https://github.com/typicode/husky)).
36
36
37
-
- No need to worry about code style as long as you have installed the dev dependencies - modified files are automatically formatted with Prettier on commit (by invoking [Git Hooks](https://git-scm.com/docs/githooks) via [husky](https://github.com/typicode/husky)).
37
+
- No need to worry about code style as long as you have installed the dev dependencies - modified files are automatically formatted with Prettier on commit (by invoking [Git Hooks](https://git-scm.com/docs/githooks) via [husky](https://github.com/typicode/husky)).
38
38
39
39
## Development Setup
40
40
@@ -48,6 +48,6 @@ $ npm i # install the dependencies of the project
48
48
49
49
A high level overview of tools used:
50
50
51
-
-[TypeScript](https://www.typescriptlang.org/) as the development language
52
-
-[ESLint](https://eslint.org/) for code-style
53
-
-[Prettier](https://prettier.io/) for code formatting
51
+
-[TypeScript](https://www.typescriptlang.org/) as the development language
52
+
-[ESLint](https://eslint.org/) for code-style
53
+
-[Prettier](https://prettier.io/) for code formatting
0 commit comments