chore: add missing GitHub mds (#95)

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to make participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+- The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all project spaces, and it also applies when
+an individual is representing the project or its community in public spaces.
+Examples of representing a project or community include using an official
+project e-mail address, posting via an official social media account, or acting
+as an appointed representative at an online or offline event. Representation of
+a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at https://discord.gg/bRCvFy9. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

.github/COMMIT_CONVENTION.md

@@ -0,0 +1,91 @@
+## Git Commit Message Convention
+
+> This is adapted from [Angular's commit convention](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-angular).
+
+#### TL;DR:
+
+Messages must be matched by the following regex:
+
+```js
+/^(revert: )?(feat|fix|docs|style|refactor|perf|test|workflow|build|ci|chore|types|wip)(\(.+\))?: .{1,72}/;
+```
+
+#### Examples
+
+Appears under "Features" header, `GuildMember` subheader:
+
+```
+feat(GuildMember): add 'tag' method
+```
+
+Appears under "Bug Fixes" header, `Guild` subheader, with a link to issue #28:
+
+```
+fix(Guild): handle events correctly
+
+close #28
+```
+
+Appears under "Performance Improvements" header, and under "Breaking Changes" with the breaking change explanation:
+
+```
+perf(core): improve patching by removing 'bar' option
+
+BREAKING CHANGE: The 'bar' option has been removed.
+```
+
+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.
+
+```
+revert: feat(Managers): add Managers
+
+This reverts commit 667ecc1654a317a13331b17617d973392f415f02.
+```
+
+### Full Message Format
+
+A commit message consists of a **header**, **body** and **footer**. The header has a **type**, **scope** and **subject**:
+
+```
+<type>(<scope>): <subject>
+<BLANK LINE>
+<body>
+<BLANK LINE>
+<footer>
+```
+
+The **header** is mandatory and the **scope** of the header is optional.
+
+### Revert
+
+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.
+
+### Type
+
+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.
+
+Other prefixes are up to your discretion. Suggested prefixes are `docs`, `chore`, `style`, `refactor`, and `test` for non-changelog related tasks.
+
+### Scope
+
+The scope could be anything specifying the place of the commit change. For example `GuildMember`, `Guild`, `Message`, `MessageEmbed` etc...
+
+### Subject
+
+The subject contains a succinct description of the change:
+
+- use the imperative, present tense: "change" not "changed" nor "changes"
+- don't capitalize the first letter
+- no dot (.) at the end
+
+### Body
+
+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.
+
+### Footer
+
+The footer should contain any information about **Breaking Changes** and is also the place to
+reference GitHub issues that this commit **Closes**.
+
+**Breaking Changes** should start with the word `BREAKING CHANGE:` with a space or two newlines. The rest of the commit message is then used for this.

.github/CONTRIBUTING.md

@@ -0,0 +1,53 @@
+# discord-api-types Contributing Guide
+
+**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/bRCvFy9) instead of opening an issue, or on [GitHub Discussions](https://github.com/discordjs/discord-api-types/discussions) – you will get redirected there anyway.**
+
+- [Code of Conduct](https://github.com/discordjs/discord-api-types/blob/main/.github/CODE_OF_CONDUCT.md)
+- [Pull Request Guidelines](#pull-request-guidelines)
+- [Development Setup](#development-setup)
+- [Project Structure](#project-structure)
+- [Contributing Tests](#contributing-tests)
+
+## Pull Request Guidelines
+
+- Checkout a topic branch from a base branch, e.g. `main`, and merge back against that branch.
+
+- If adding a new feature:
+
+  - Provide a convincing reason to add this feature. Ideally, you should open a suggestion issue first and have it approved before working on it.
+
+- If fixing a bug:
+
+  - 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.
+
+  ```
+  fix(Guild): handle events correctly
+
+  close #28
+  ```
+
+  - Provide a detailed description of the bug in the PR. Live demo preferred.
+
+- It's OK to have multiple small commits as you work on the PR - GitHub can automatically squash them before merging.
+
+- Make sure tests pass!
+
+- 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)).
+
+- 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)).
+
+## Development Setup
+
+You will need [Node.js](http://nodejs.org) **version 12+**, and [npm](https://www.npmjs.com/).
+
+After cloning the repo, run:
+
+```bash
+$ npm i # install the dependencies of the project
+```
+
+A high level overview of tools used:
+
+- [TypeScript](https://www.typescriptlang.org/) as the development language
+- [ESLint](https://eslint.org/) for code-style
+- [Prettier](https://prettier.io/) for code formatting

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,25 @@
+---
+name: Bug report
+about: Report incorrect or unexpected behavior of discord-api-types
+title: ''
+labels: 'bug'
+assignees: ''
+---
+
+<!-- Use Discord for questions: https://discord.gg/bRCvFy9 -->
+
+**Please describe the problem you are having in as much detail as possible:**
+
+**Include a reproducible code sample here, if possible:**
+
+```ts
+// Place your code here
+```
+
+**Further details:**
+
+- Runtime:
+  <!-- Complete whichever is applicable -->
+  - Node.js version:
+  - deno version:
+- Priority this issue should have – please be realistic and elaborate if possible:

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Discord server
+    url: https://discord.gg/bRCvFy9
+    about: Please visit our Discord server for questions and support requests.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,21 @@
+---
+name: Feature request
+about: Request a feature for the discord-api-types library
+title: ''
+labels: 'discussion'
+assignees: ''
+---
+
+<!-- Use Discord for questions: https://discord.gg/bRCvFy9 -->
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Eg. I'm always frustrated when [...]
+
+**Describe the ideal solution**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,3 @@
+**Please describe the changes this PR makes and why it should be merged:**
+
+**Reference Discord API Docs PRs or commits:**

.github/SUPPORT.md

@@ -0,0 +1,8 @@
+# Seeking support?
+
+We only use this issue tracker for bug reports and feature request. We are not able to provide general support or answer questions in the form of GitHub issues.
+
+For general questions about discord-api-types installation and use please ask in [GitHub Discussions](https://github.com/discordjs/discord-api-types/discussions),
+or in the dedicated support channels in our Discord server: https://discord.gg/bRCvFy9
+
+Any issues that don't directly involve a bug or a feature request will likely be closed and redirected.

.npmrc

@@ -0,0 +1,4 @@
+audit=false
+fund=false
+node-version=false
+legacy-peer-deps=true

package.json

@@ -19,19 +19,19 @@
 		}
 	},
 	"scripts": {
-		"prepublishOnly": "run-s clean test:lint build:node",
-		"postpublish": "run-s clean:node build:deno",
+		"build:ci": "tsc --noEmit --incremental false",
 		"build:deno": "node ./scripts/deno.mjs",
 		"build:node": "tsc && run-p esm:*",
-		"build:ci": "tsc --noEmit --incremental false",
+		"clean:deno": "rimraf deno/",
+		"clean:node": "rimraf {v*,default,common}/**/*.{js,mjs,d.ts,map}",
+		"clean": "run-p clean:*",
 		"esm:common": "gen-esm-wrapper ./common/index.js ./common/index.mjs",
 		"esm:v6": "gen-esm-wrapper ./v6/index.js ./v6/index.mjs",
 		"esm:v8": "gen-esm-wrapper ./v8/index.js ./v8/index.mjs",
 		"lint": "eslint --fix --ext mjs,js,ts {v*,default,common}/**",
-		"test:lint": "eslint --ext mjs,js,ts {v*,default,common}/**",
-		"clean": "run-p clean:*",
-		"clean:node": "rimraf {v*,default,common}/**/*.{js,mjs,d.ts,map}",
-		"clean:deno": "rimraf deno/"
+		"postpublish": "run-s clean:node build:deno",
+		"prepublishOnly": "run-s clean test:lint build:node",
+		"test:lint": "eslint --ext mjs,js,ts {v*,default,common}/**"
 	},
 	"keywords": [
 		"discord",
@@ -53,21 +53,22 @@
 		"node": ">=12"
 	},
 	"devDependencies": {
-		"@commitlint/cli": "^11.0.0",
-		"@commitlint/config-angular": "^11.0.0",
-		"@typescript-eslint/eslint-plugin": "^4.14.2",
-		"@typescript-eslint/parser": "^4.14.2",
-		"eslint": "^7.19.0",
-		"eslint-config-marine": "^8.1.0",
-		"eslint-config-prettier": "^7.2.0",
+		"@commitlint/cli": "^12.0.1",
+		"@commitlint/config-angular": "^12.0.1",
+		"@typescript-eslint/eslint-plugin": "^4.18.0",
+		"@typescript-eslint/parser": "^4.18.0",
+		"eslint": "^7.22.0",
+		"eslint-config-marine": "^8.3.2",
+		"eslint-config-prettier": "^8.1.0",
 		"eslint-plugin-prettier": "^3.3.1",
 		"gen-esm-wrapper": "^1.1.1",
 		"husky": "^4.3.8",
 		"lint-staged": "^10.5.4",
 		"npm-run-all": "^4.1.5",
 		"prettier": "^2.2.1",
+		"pretty-quick": "^3.1.0",
 		"rimraf": "^3.0.2",
-		"typescript": "^4.1.3"
+		"typescript": "^4.2.3"
 	},
 	"repository": {
 		"type": "git",
@@ -87,7 +88,7 @@
 	},
 	"husky": {
 		"hooks": {
-			"pre-commit": "lint-staged",
+			"pre-commit": "pretty-quick --staged && lint-staged && npm run build:deno && git add deno",
 			"commit-msg": "commitlint -E HUSKY_GIT_PARAMS"
 		}
 	},