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 taking the time to contribute to this plugin!
2
+
3
+
This guide will walk you through the contribution workflow - from [reporting issues](#reporting-issues) and [making changes](#making-changes), to [submitting a pull request](#pull-requests) and [testing the plugin](#testing-the-plugin).
4
+
5
+
# Getting started
6
+
## Reporting Issues
7
+
### 1. Check for existing issues
8
+
If you encounter a problem, first <ahref="../../../issues">search the issue tracker</a> to see if it has already been reported.
9
+
- If an there is an existing issue and you can provide additional information add a comment with your information.
10
+
- If you just want to indicate that you are experiencing the same issue, add a :+1: reaction to the issue.
11
+
### 2. Create a new Issue
12
+
If not related issue exists, open a new one using the appropriate <ahref="../../../issues/new/choose">issue form</a>.
13
+
14
+
## Working on an Issue
15
+
#### 1. Browse <ahref="../../../issues">existing issues</a> to find something you'd like to work on.
16
+
#### 2. Comment on the issue to let others know you're working on it.
17
+
#### 3. Follow the [making changes](#making-changes) guide below.
18
+
#### 4. When ready, submit a [pull request](#pull-request).
19
+
20
+
## Making Changes
21
+
### What you need:
22
+
-[**Git**](https://git-scm.com/) on your local machine.
23
+
-[**Node.js**](https://nodejs.org/en) at least version `18.x`.
24
+
- Code editor, such as [Visual Studio Code](https://code.visualstudio.com/)
25
+
### Start working:
26
+
#### 1. Fork the repository.
27
+
#### 2. Create a new vault
28
+
Just for testing the plugin so you **can't** exedentially destroy your real vault
29
+
#### 3. Clone repository to your local machine.
30
+
```shell
31
+
cd path/to/vault
32
+
mkdir .obsidian/plugins
33
+
cd .obsidian/plugins
34
+
git clone <your-fork-url><plugin-id>
35
+
```
36
+
#### 4. Install dependencies
37
+
```shell
38
+
cd<plugin-id>
39
+
npm install
40
+
```
41
+
#### 5. Create a working branch
42
+
```shell
43
+
git checkout -b <working-branch>
44
+
```
45
+
#### 6. Compile the source code
46
+
The following command keeps running in the terminal and rebuilds the plugin when you modify the source code.
47
+
```shell
48
+
npm run dev
49
+
```
50
+
#### 7. Enable the plugin in Obsidian settings
51
+
> [!TIP]
52
+
> Install the [Hot-Reload](https://github.com/pjeby/hot-reload) plugin to automatically reload the plugin while developing.
53
+
54
+
## Committing Your Changes
55
+
#### 1. Check the formatting of your code
56
+
Before committing the following command will fix most of the formatting issues according to our ESLint configuration.
57
+
```shell
58
+
npm run lint-fix
59
+
```
60
+
If you see the following output without any errors the formatting matches the the requirements if any errors remain, fix them manually before proceeding.
61
+
```output
62
+
> eslint . --fix --config .eslintrc.release
63
+
```
64
+
#### 2. Create commit
65
+
Than commit your changes with a clear, descriptive commit message.
66
+
67
+
## Pull Requests
68
+
#### 1. Run tests before submitting
69
+
```shell
70
+
npm run test
71
+
```
72
+
- Ensure all tests pass.
73
+
- If new tests are needed, add them or note what should be tested in your PR.
74
+
#### 2. Push your Branch to your fork
75
+
#### 3. Open a Pull Request using the provided template
76
+
#### 4. Reference any related issues
77
+
78
+
## Testing the Plugin
79
+
*Not a developer* but still want to help? You can help with testing:
80
+
- Test the latest <ahref="../../../releases">release</a> for problems
81
+
- Test <ahref="../../../releases">pre-releases</a>
82
+
### How to test
83
+
#### 1. Do **not** test in your actual vault - create new vault just for testing
84
+
#### 2. Install the version you want to test in the vault
85
+
#### 3. If you found a bug or unexpected behavior
86
+
- Checkout [reporting issues](#reporting-issues)
87
+
- Make sure you know how to reproduce the bug
88
+
- Mention the version you have tested
89
+
- Provide screenshots/videos or your testfiles to make it easier to reproduce
0 commit comments