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: CODE-OF-CONDUCT.md
+40-11
Original file line number
Diff line number
Diff line change
@@ -2,11 +2,17 @@
2
2
3
3
## Our Pledge
4
4
5
-
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.
5
+
In the interest of fostering an open and welcoming environment, we as
6
+
contributors and maintainers pledge to make participation in our project and our
7
+
community a harassment-free experience for everyone, regardless of age, body
8
+
size, disability, ethnicity, sex characteristics, gender identity and
9
+
expression, level of experience, education, socio-economic status, nationality,
10
+
personal appearance, race, religion, or sexual identity and orientation.
6
11
7
12
## Our Standards
8
13
9
-
Examples of behavior that contributes to creating a positive environment include:
14
+
Examples of behavior that contributes to creating a positive environment
15
+
include:
10
16
11
17
- Using welcoming and inclusive language
12
18
- Being respectful of differing viewpoints and experiences
@@ -16,31 +22,54 @@ Examples of behavior that contributes to creating a positive environment include
16
22
17
23
Examples of unacceptable behavior by participants include:
18
24
19
-
- The use of sexualized language or imagery and unwelcome sexual attention or advances
25
+
- The use of sexualized language or imagery and unwelcome sexual attention or
26
+
advances
20
27
- Trolling, insulting/derogatory comments, and personal or political attacks
21
28
- Public or private harassment
22
-
- Publishing others' private information, such as a physical or electronic address, without explicit permission
23
-
- Other conduct which could reasonably be considered inappropriate in a professional setting
29
+
- Publishing others' private information, such as a physical or electronic
30
+
address, without explicit permission
31
+
- Other conduct which could reasonably be considered inappropriate in a
32
+
professional setting
24
33
25
34
## Our Responsibilities
26
35
27
-
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.
36
+
Project maintainers are responsible for clarifying the standards of acceptable
37
+
behavior and are expected to take appropriate and fair corrective action in
38
+
response to any instances of unacceptable behavior.
28
39
29
-
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.
40
+
Project maintainers have the right and responsibility to remove, edit, or reject
41
+
comments, commits, code, wiki edits, issues, and other contributions that are
42
+
not aligned to this Code of Conduct, or to ban temporarily or permanently any
43
+
contributor for other behaviors that they deem inappropriate, threatening,
44
+
offensive, or harmful.
30
45
31
46
## Scope
32
47
33
-
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.
48
+
This Code of Conduct applies within all project spaces, and it also applies when
49
+
an individual is representing the project or its community in public spaces.
50
+
Examples of representing a project or community include using an official
51
+
project e-mail address, posting via an official social media account, or acting
52
+
as an appointed representative at an online or offline event. Representation of
53
+
a project may be further defined and clarified by project maintainers.
34
54
35
55
## Enforcement
36
56
37
-
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project admin at [email protected]. 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.
57
+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
58
+
reported by contacting the project admin at [email protected]. All complaints
59
+
will be reviewed and investigated and will result in a response that is deemed
60
+
necessary and appropriate to the circumstances. The project team is obligated to
61
+
maintain confidentiality with regard to the reporter of an incident. Further
62
+
details of specific enforcement policies may be posted separately.
38
63
39
-
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.
64
+
Project maintainers who do not follow or enforce the Code of Conduct in good
65
+
faith may face temporary or permanent repercussions as determined by other
66
+
members of the project's leadership.
40
67
41
68
## Attribution
42
69
43
-
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
70
+
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
Thanks for reaching the project and wanting to improve the extension! This file has few guidelines that will help you along the way.
3
+
Thanks for reaching the project and wanting to improve the extension! This file
4
+
has few guidelines that will help you along the way.
4
5
5
6
## Code of Conduct
6
7
7
-
Please, make sure you read the [Code of Conduct](CODE-OF-CONDUCT.md) file before contributing! It is short, it will not take you much time :wink:!
8
+
Please, make sure you read the [Code of Conduct](CODE-OF-CONDUCT.md) file before
9
+
contributing! It is short, it will not take you much time :wink:!
8
10
9
11
## How to
10
12
11
13
### Issue
12
14
13
-
The first thing would be to create an issue, which would notify the contributors. Furthermore, it gives more visibility to the problem or feature and may attract other people on helping. You can propose a solution to the issue by creating a pull request. If you do not feel like contributing, no worries, a maintainer will come to help!
15
+
The first thing would be to create an issue, which would notify the
16
+
contributors. Furthermore, it gives more visibility to the problem or feature
17
+
and may attract other people on helping. You can propose a solution to the issue
18
+
by creating a pull request. If you do not feel like contributing, no worries, a
19
+
maintainer will come to help!
14
20
15
21
### Developing
16
22
17
23
When developing, make sure to following the below steps:
18
24
19
25
1. Fork the repository.
20
-
2. Clone the repository to your local machine, adding the original repo as an upstream remote:
26
+
2. Clone the repository to your local machine, adding the original repo as an
```sh git checkout main git pull upstream main ```
36
38
37
39
4. Install all the dependencies:
38
40
39
-
```sh
40
-
yarn
41
-
```
41
+
```sh yarn ```
42
42
43
43
5. Create the new branch:
44
44
45
-
```sh
46
-
git checkout -b branch-with-sense
47
-
```
45
+
```sh git checkout -b branch-with-sense ```
48
46
49
47
6. Save changes and push to your fork:
50
48
51
-
```sh
52
-
git push -u origin HEAD
53
-
```
49
+
```sh git push -u origin HEAD ```
54
50
55
-
7. Create a pull request with your changes. Make sure that your base branch is set to `next`, not `main`.
51
+
7. Create a pull request with your changes.
56
52
57
53
#### Commits
58
54
59
-
The repository uses semantic commits, since it generates the changelog automatically. Whenever you commit your changes, husky will run the git hooks which will:
55
+
Make sure to commit using semantic commits. Also, its recommended to:
60
56
61
-
1. Check for the linting, using ESLint (see the [config file](.eslintrc.json)).
62
-
2. Check for the style and fixing it, using Prettier (see the [config file](.prettierrc)).
63
-
3. Prompt you with the commitizen CLI tool. See the semantic commits [documentation](https://www.conventionalcommits.org/en/v1.0.0/) for more info.
57
+
- Check for the linting and formatting, using ESLint (see the [config file](.eslintrc.json)).
58
+
- Add a changeset to your changes, with `bun changeset`.
64
59
65
60
#### Merging a PR
66
61
67
-
After your code has been reviewed and approved, one of the administrators will squash the changes to the base branch.
62
+
After your code has been reviewed and approved, one of the administrators will
63
+
squash the changes to the base branch.
68
64
69
65
## License
70
66
71
-
By contributing your code to this repository, you agree to license your contribution under the [MIT License](LICENSE).
67
+
By contributing your code to this repository, you agree to license your
0 commit comments