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: CONTRIBUTING.md
+39-32Lines changed: 39 additions & 32 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,80 +1,87 @@
1
1
# Contributing to Overseerr
2
2
3
-
All help is welcome and greatly appreciated. If you would like to contribute to the project, the instructions below can get you started...
3
+
All help is welcome and greatly appreciated! If you would like to contribute to the project, the following instructions should get you started...
4
4
5
5
## Development
6
6
7
7
### Tools Required
8
8
9
-
- HTML/Typescript/Javascript editor of choice. ([VSCode](https://code.visualstudio.com/) is recommended. Upon opening the project, a few extensions will be automatically recommended for install.)
10
-
-[NodeJS](https://nodejs.org/en/download/) (Node 12.x.x or higher)
9
+
- HTML/Typescript/Javascript editor
10
+
-[VSCode](https://code.visualstudio.com/) is recommended. Upon opening the project, a few extensions will be automatically recommended for install.
11
+
-[NodeJS](https://nodejs.org/en/download/) (Node 14.x or higher)
11
12
-[Yarn](https://yarnpkg.com/)
12
13
-[Git](https://git-scm.com/downloads)
13
14
14
15
### Getting Started
15
16
16
-
1.[Fork](https://help.github.com/articles/fork-a-repo/) the repository to your own GitHub account and then [clone](https://help.github.com/articles/cloning-a-repository/) it to your local device.
17
+
1.[Fork](https://help.github.com/articles/fork-a-repo/) the repository to your own GitHub account and [clone](https://help.github.com/articles/cloning-a-repository/) it to your local device:
- It is recommended to name the branch something relevant to the feature or fix you are working on.
36
-
- An example of this would be `fix-title-cards` or `feature-new-system`.
37
-
- Bad examples would be `patch` or `bug`.
36
+
- It is recommended to give your branch a meaningful name, relevant to the feature or fix you are working on.
37
+
- Good examples:
38
+
-`docs-docker`
39
+
-`feature-new-system`
40
+
-`fix-title-cards`
41
+
- Bad examples:
42
+
-`bug`
43
+
-`docs`
44
+
-`feature`
45
+
-`fix`
46
+
-`patch`
38
47
39
-
4. Run development environment
48
+
4. Run the development environment:
40
49
41
50
```bash
42
51
yarn
43
52
yarn dev
44
53
```
45
54
46
-
- Alternatively you can run using[Docker](https://www.docker.com/) with `docker-compose up -d`. This method does not require installing NodeJS or Yarn on your machine directly.
55
+
- Alternatively, you can use[Docker](https://www.docker.com/) with `docker-compose up -d`. This method does not require installing NodeJS or Yarn on your machine directly.
47
56
48
-
5. Create your patch and run appropriate tests.
57
+
5. Create your patch and test your changes.
49
58
50
-
6. Follow the [guidelines](#contributing-code).
51
-
52
-
7. Should you need to update your fork, you can do so by rebasing from `upstream`:
53
-
54
-
```bash
55
-
git fetch upstream
56
-
git rebase upstream/develop
57
-
git push origin BRANCH_NAME -f
58
-
```
59
+
- Be sure to follow both the [code](#contributing-code) and [UI text](#ui-text-style) guidelines.
60
+
- Should you need to update your fork, you can do so by rebasing from `upstream`:
61
+
```bash
62
+
git fetch upstream
63
+
git rebase upstream/develop
64
+
git push origin BRANCH_NAME -f
65
+
```
59
66
60
67
### Contributing Code
61
68
62
-
- If you are taking on an existing bug or feature ticket, please comment on the [GitHub Issue](https://github.com/sct/overseerr/issues) to avoid multiple people working on the same thing.
69
+
- If you are taking on an existing bug or feature ticket, please comment on the [issue](https://github.com/sct/overseerr/issues) to avoid multiple people working on the same thing.
63
70
- All commits **must** follow [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/)
64
-
- It is okay if you squash your PR down to be a single commit that fits this standard.
65
-
-PRs with commits not following this standard will not be merged.
71
+
- It is okay to squash your pull request down into a single commit that fits this standard.
72
+
- Pull requests with commits not following this standard will **not** be merged.
66
73
- Please make meaningful commits, or squash them.
67
-
- Always rebase your commit to the latest `develop` branch. Do not merge `develop` into your branch.
68
-
- It is your responsibility to keep your branch up to date. It will not be merged unless its rebased off the latest `develop` branch.
74
+
- Always rebase your commit to the latest `develop` branch. Do **not** merge `develop` into your branch.
75
+
- It is your responsibility to keep your branch up-to-date. Your work will **not** be merged unless it is rebased off the latest `develop` branch.
69
76
- You can create a "draft" pull request early to get feedback on your work.
70
-
- Your code must be formatted correctly or the tests will fail.
71
-
- We use Prettier to format our codebase. It should automatically run with a `git` hook, but it is recommended to have the Prettier extension installed in your editor and format on save.
72
-
- If you have questions or need help, you can reach out in [GitHub Discussions](https://github.com/sct/overseerr/discussions) or in our [Discord](https://discord.gg/PkCWJSeCk7).
73
-
- Only open pull requests to `develop`. Never`master`. Any PRs opened to `master` will be closed.
77
+
- Your code **must** be formatted correctly, or the tests will fail.
78
+
- We use Prettier to format our code base. It should automatically run with a Git hook, but it is recommended to have the Prettier extension installed in your editor and format on save.
79
+
- If you have questions or need help, you can reach out via [Discussions](https://github.com/sct/overseerr/discussions) or our [Discord server](https://discord.gg/PkCWJSeCk7).
80
+
- Only open pull requests to `develop`, never`master`! Any pull requests opened to `master` will be closed.
74
81
75
82
### UI Text Style
76
83
77
-
When adding new UI text, please be sure to adhere to the following guidelines:
84
+
When adding new UI text, please try to adhere to the following guidelines:
78
85
79
86
1. Be concise and clear, and use as few words as possible to make your point.
80
87
2. Use the Oxford comma where appropriate.
@@ -90,7 +97,7 @@ When adding new UI text, please be sure to adhere to the following guidelines:
90
97
91
98
## Translation
92
99
93
-
We use [Weblate](https://hosted.weblate.org/engage/overseerr/) for our translations, and your help with localizing Overseerr would be greatly appreciated! If your language is not listed below, please [open a feature request on GitHub](https://github.com/sct/overseerr/issues/new/choose).
100
+
We use [Weblate](https://hosted.weblate.org/engage/overseerr/) for our translations, and your help with localizing Overseerr would be greatly appreciated! If your language is not listed below, please [open a feature request](https://github.com/sct/overseerr/issues/new/choose).
0 commit comments