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
Thank you for your interest in contributing to Sonarr ("We" or "Us").
3
+
Thank you for your interest in contributing to Lidarr ("We" or "Us").
4
4
This contributor agreement ("Agreement") documents the rights granted by contributors to Us. To make this document effective, please complete the form below. This is a legally binding document, so please read it carefully before agreeing to it. The Agreement may cover more than one software project managed by Us.
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# How to Contribute #
2
2
3
-
We're always looking for people to help make Sonarr even better, there are a number of ways to contribute.
3
+
We're always looking for people to help make Lidarr even better, there are a number of ways to contribute.
4
4
5
5
## Documentation ##
6
6
Setup guides, FAQ, the more information we have on the wiki the better.
@@ -15,7 +15,7 @@ Setup guides, FAQ, the more information we have on the wiki the better.
15
15
16
16
### Getting started ###
17
17
18
-
1. Fork Sonarr
18
+
1. Fork Lidarr
19
19
2. Clone (develop branch) *you may need pull in submodules separately if you client doesn't clone them automatically (CurlSharp)*
20
20
3. Run `npm install`
21
21
4. Run `npm start` - Used to compile the UI components and copy them.
@@ -24,8 +24,8 @@ Setup guides, FAQ, the more information we have on the wiki the better.
24
24
5. Compile in Visual Studio
25
25
26
26
### Contributing Code ###
27
-
- If you're adding a new, already requested feature, please comment on [Github Issues](https://github.com/Sonarr/Sonarr/issues"Github Issues") so work is not duplicated (If you want to add something not already on there, please talk to us first)
28
-
- Rebase from Sonarr's develop branch, don't merge
27
+
- If you're adding a new, already requested feature, please comment on [Github Issues](https://github.com/lidarr/Lidarr/issues"Github Issues") so work is not duplicated (If you want to add something not already on there, please talk to us first)
28
+
- Rebase from Lidarr's develop branch, don't merge
29
29
- Make meaningful commits, or squash them
30
30
- Feel free to make a pull request before work is complete, this will let us see where its at and make comments/suggest improvements
31
31
- Reach out to us on the forums or on IRC if you have any questions
0 commit comments