mirror of
https://github.com/veganhacktivists/arabot.git
synced 2025-11-29 09:18:28 +01:00
refactor: run prettier
This commit is contained in:
Anthony Berg
@@ -17,23 +17,23 @@ diverse, inclusive, and healthy community.
|
||||
Examples of behavior that contributes to a positive environment for our
|
||||
community include:
|
||||
|
||||
* Demonstrating empathy and kindness toward other people
|
||||
* Being respectful of differing opinions, viewpoints, and experiences
|
||||
* Giving and gracefully accepting constructive feedback
|
||||
* Accepting responsibility and apologizing to those affected by our mistakes,
|
||||
- Demonstrating empathy and kindness toward other people
|
||||
- Being respectful of differing opinions, viewpoints, and experiences
|
||||
- Giving and gracefully accepting constructive feedback
|
||||
- Accepting responsibility and apologizing to those affected by our mistakes,
|
||||
and learning from the experience
|
||||
* Focusing on what is best not just for us as individuals, but for the
|
||||
- Focusing on what is best not just for us as individuals, but for the
|
||||
overall community
|
||||
|
||||
Examples of unacceptable behavior include:
|
||||
|
||||
* The use of sexualized language or imagery, and sexual attention or
|
||||
- The use of sexualized language or imagery, and sexual attention or
|
||||
advances of any kind
|
||||
* Trolling, insulting or derogatory comments, and personal or political attacks
|
||||
* Public or private harassment
|
||||
* Publishing others' private information, such as a physical or email
|
||||
- Trolling, insulting or derogatory comments, and personal or political attacks
|
||||
- Public or private harassment
|
||||
- Publishing others' private information, such as a physical or email
|
||||
address, without their explicit permission
|
||||
* Other conduct which could reasonably be considered inappropriate in a
|
||||
- Other conduct which could reasonably be considered inappropriate in a
|
||||
professional setting
|
||||
|
||||
## Enforcement Responsibilities
|
||||
@@ -106,7 +106,7 @@ Violating these terms may lead to a permanent ban.
|
||||
### 4. Permanent Ban
|
||||
|
||||
**Community Impact**: Demonstrating a pattern of violation of community
|
||||
standards, including sustained inappropriate behavior, harassment of an
|
||||
standards, including sustained inappropriate behavior, harassment of an
|
||||
individual, or aggression toward or disparagement of classes of individuals.
|
||||
|
||||
**Consequence**: A permanent ban from any sort of public interaction within
|
||||
|
||||
@@ -1,11 +1,12 @@
|
||||
# Commands for the bot
|
||||
|
||||
These are all the commands that you can use for the bot. Some of these are for staff only, but everyone can use the
|
||||
These are all the commands that you can use for the bot. Some of these are for staff only, but everyone can use the
|
||||
general commands
|
||||
|
||||
## Contents
|
||||
|
||||
- [General](commands/GENERAL.md)
|
||||
- [Moderator](commands/MOD.md)
|
||||
- [Verifier](commands/VERIFIER.md)
|
||||
- [Mentor](commands/MENTOR.md)
|
||||
- [Coordinator](commands/COORDINATOR.md)
|
||||
- [Coordinator](commands/COORDINATOR.md)
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# Commit Message Format
|
||||
# Commit Message Format
|
||||
|
||||
*This specification is a modified version of the [AngularJS commit message format](https://github.com/angular/angular/blob/main/CONTRIBUTING.md#-commit-message-format).*
|
||||
_This specification is a modified version of the [AngularJS commit message format](https://github.com/angular/angular/blob/main/CONTRIBUTING.md#-commit-message-format)._
|
||||
|
||||
We have very precise rules over how our Git commit messages must be formatted.
|
||||
This format leads to **easier to read commit history**.
|
||||
|
||||
Each commit message consists of a **header**, a **body**, and a **footer**.
|
||||
|
||||
|
||||
```
|
||||
<header>
|
||||
<BLANK LINE>
|
||||
@@ -23,7 +22,6 @@ When the body is present it must be at least 20 characters long and must conform
|
||||
|
||||
The `footer` is optional. The [Commit Message Footer](#commit-footer) format describes what the footer is used for and the structure it must have.
|
||||
|
||||
|
||||
#### <a name="commit-header"></a>Commit Message Header
|
||||
|
||||
```
|
||||
@@ -38,42 +36,39 @@ The `footer` is optional. The [Commit Message Footer](#commit-footer) format des
|
||||
|
||||
The `<type>` and `<summary>` fields are mandatory, the `(<scope>)` field is optional.
|
||||
|
||||
|
||||
##### Type
|
||||
|
||||
Must be one of the following:
|
||||
|
||||
* **build**: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
|
||||
* **ci**: Changes to our CI configuration files and scripts
|
||||
* **docs**: Documentation only changes
|
||||
* **feat**: A new feature
|
||||
* **fix**: A bug fix
|
||||
* **perf**: A code change that improves performance
|
||||
* **refactor**: A code change that neither fixes a bug nor adds a feature
|
||||
* **test**: Adding missing tests or correcting existing tests
|
||||
|
||||
- **build**: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
|
||||
- **ci**: Changes to our CI configuration files and scripts
|
||||
- **docs**: Documentation only changes
|
||||
- **feat**: A new feature
|
||||
- **fix**: A bug fix
|
||||
- **perf**: A code change that improves performance
|
||||
- **refactor**: A code change that neither fixes a bug nor adds a feature
|
||||
- **test**: Adding missing tests or correcting existing tests
|
||||
|
||||
##### Scope
|
||||
|
||||
The scope should be the name of the npm package affected (as perceived by the person reading the changelog generated from commit messages).
|
||||
|
||||
The following is the list of supported scopes:
|
||||
|
||||
* `arabot`
|
||||
* `config`
|
||||
* `compiler`
|
||||
* `database`
|
||||
* `docs`
|
||||
* `upgrade`
|
||||
|
||||
- `arabot`
|
||||
- `config`
|
||||
- `compiler`
|
||||
- `database`
|
||||
- `docs`
|
||||
- `upgrade`
|
||||
|
||||
##### Summary
|
||||
|
||||
Use the summary field to provide 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
|
||||
|
||||
- use the imperative, present tense: "change" not "changed" nor "changes"
|
||||
- don't capitalize the first letter
|
||||
- no dot (.) at the end
|
||||
|
||||
#### <a name="commit-body"></a>Commit Message Body
|
||||
|
||||
@@ -82,7 +77,6 @@ Just as in the summary, use the imperative, present tense: "fix" not "fixed" nor
|
||||
Explain the motivation for the change in the commit message body. This commit message should explain _why_ you are making the change.
|
||||
You can include a comparison of the previous behavior with the new behavior in order to illustrate the impact of the change.
|
||||
|
||||
|
||||
#### <a name="commit-footer"></a>Commit Message Footer
|
||||
|
||||
The footer can contain information about breaking changes and deprecations and is also the place to reference GitHub issues, Jira tickets, and other PRs that this commit closes or is related to.
|
||||
@@ -112,7 +106,6 @@ Breaking Change section should start with the phrase "BREAKING CHANGE: " followe
|
||||
|
||||
Similarly, a Deprecation section should start with "DEPRECATED: " followed by a short description of what is deprecated, a blank line, and a detailed description of the deprecation that also mentions the recommended update path.
|
||||
|
||||
|
||||
### Revert commits
|
||||
|
||||
If the commit reverts a previous commit, it should begin with `revert: `, followed by the header of the reverted commit.
|
||||
|
||||
@@ -5,8 +5,8 @@
|
||||
- `/ping`/`?ping` - Checks if the bot is alive and the ping of the bot.
|
||||
- `/apply`/`?apply` - Gives you the link to where you can apply to be a Moderator or Verifier.
|
||||
- `/count`/`?count` - Tells you how many vegans and non-vegans there are on the server.
|
||||
- `/info <info> <optional: visible>` - Gives you information based on what you pick in `<info>`. If you make `visible`
|
||||
true, it will make the information visible to everyone.
|
||||
- `/info <info> <optional: visible>` - Gives you information based on what you pick in `<info>`. If you make `visible`
|
||||
true, it will make the information visible to everyone.
|
||||
- `/help`/`?help` - Gives a link (here) to all the commands.
|
||||
|
||||
## Economy
|
||||
@@ -18,7 +18,7 @@ true, it will make the information visible to everyone.
|
||||
## XP
|
||||
|
||||
- `/rank <optional: user>`/`?rank <optional: user>` - Shows your rank based on the amount of XP you have. If you provide
|
||||
a user, it will display that user's rank instead.
|
||||
a user, it will display that user's rank instead.
|
||||
|
||||
## Fun Commands
|
||||
|
||||
@@ -29,4 +29,4 @@ a user, it will display that user's rank instead.
|
||||
- `/poke`
|
||||
- `/sad`
|
||||
- `/shrug`
|
||||
- `/cringe`
|
||||
- `/cringe`
|
||||
|
||||
@@ -4,12 +4,12 @@
|
||||
|
||||
- `/rename <user> <optional: nickname>`/`?ru <user> <optional: nickname>` - Renames that user to the specified nickname,
|
||||
if nickname is left blank it will reset the nickname to their original username.
|
||||
- `/slowmode <duration>`/`?slowmode <duration>` - changes the slowmode for a chat. Duration uses a time which can be set by providing a number
|
||||
followed by s/d/m/y or just writing `off`. These can be combined.
|
||||
For example to set the slowmode for 1 minute and 30 seconds, you would write: `1m 30s`.
|
||||
- `/slowmode <duration>`/`?slowmode <duration>` - changes the slowmode for a chat. Duration uses a time which can be set by providing a number
|
||||
followed by s/d/m/y or just writing `off`. These can be combined.
|
||||
For example to set the slowmode for 1 minute and 30 seconds, you would write: `1m 30s`.
|
||||
- `/softmute <user>`/`?sm/softmute <user>` - Prevents the user from reacting to messages.
|
||||
- `/vcmute <user>`/`?vcmute <user>` - Adds a persistent VC mute if the user has left the VC or leaves the server to
|
||||
circumvent VC mutes.
|
||||
- `/vcmute <user>`/`?vcmute <user>` - Adds a persistent VC mute if the user has left the VC or leaves the server to
|
||||
circumvent VC mutes.
|
||||
- `?warn <user> <reason>` - Gives a warning to the user.
|
||||
|
||||
## Roles
|
||||
@@ -36,15 +36,15 @@ These are used for users that have broken rules severe enough that takes away th
|
||||
|
||||
- `/restrict <user> <reason>`/`?r/restrict <user> <reason>` - Restricts the user to the restricted section
|
||||
- `/unrestrict <user>`/`?ur <user>` - Unrestricts the user
|
||||
- `/restrictlogs <optional: user>` - Shows the logs of when the user has been restricted. The need to provide the user
|
||||
is optional depending on if the command is run in the ModMail category.
|
||||
- `/restrictlogs <optional: user>` - Shows the logs of when the user has been restricted. The need to provide the user
|
||||
is optional depending on if the command is run in the ModMail category.
|
||||
- `/restricttools channel delete <optional: user>` - Deletes the vegan restricted channel for the user. Providing a user
|
||||
is only optional if the command is run in the channel that is to be deleted.
|
||||
is only optional if the command is run in the channel that is to be deleted.
|
||||
|
||||
## Bans
|
||||
|
||||
- `/tempban <user> <duration> <reason>`/`?tempban <user> <duration <reason>` - Bans the user for a specific amount of
|
||||
time. Duration uses a time which can be set by providing a number followed by s/d/m/y. These can be combined.
|
||||
For example to ban someone for 1 week and 3 days, you would write: `1w 3d`.
|
||||
time. Duration uses a time which can be set by providing a number followed by s/d/m/y. These can be combined.
|
||||
For example to ban someone for 1 week and 3 days, you would write: `1w 3d`.
|
||||
- `/ban <user> <reason>`/`?ban <user> <reason>` - Permanently bans that user.
|
||||
- `/unban <user>`/`?unban <user>` - Unbans that user.
|
||||
|
||||
@@ -2,9 +2,10 @@
|
||||
|
||||
## Verification
|
||||
|
||||
- `/verify <user> <roles>`/`?ver <user> <roles>` - This is a manual verification to give roles to a user. This should
|
||||
not be used if you are verifying the user in the voice channel. Roles available (you can write multiple in one command
|
||||
such as `v a t`):
|
||||
- `/verify <user> <roles>`/`?ver <user> <roles>` - This is a manual verification to give roles to a user. This should
|
||||
not be used if you are verifying the user in the voice channel. Roles available (you can write multiple in one command
|
||||
such as `v a t`):
|
||||
|
||||
- `v` - Vegan
|
||||
- `a` - Activist
|
||||
- `t` - Trusted
|
||||
@@ -13,8 +14,8 @@ such as `v a t`):
|
||||
- `conv` - Convinced
|
||||
- `veg` - Veg Curious
|
||||
|
||||
- `/verifytimeoutremove <user>` - Removes a verification timeout if the user has been timed out as a verifier was not
|
||||
available. This cannot be used for users that have been verified.
|
||||
- `/verifytimeoutremove <user>` - Removes a verification timeout if the user has been timed out as a verifier was not
|
||||
available. This cannot be used for users that have been verified.
|
||||
|
||||
## Roles
|
||||
|
||||
|
||||
Reference in New Issue
Block a user