Skip to content

Commit 1f3cb4e

Browse files
committed
fix: readme data link
fix: contributing.md
1 parent 72bcbb0 commit 1f3cb4e

2 files changed

Lines changed: 15 additions & 1 deletion

File tree

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -127,7 +127,7 @@ For more detailed use cases please see our [examples](examples).
127127

128128
## Data
129129

130-
Before running the examples, one can use the data from the [blocksnet-data](tests/data) repository releases and place it in the
130+
Before running the examples, one can use the data from the [blocksnet-data](https://github.com/IDUclub/blocksnet-data/releases) repository releases and place it in the
131131
`examples/data` directory, for example:
132132

133133
```

docs/source/blocksnet/contributing.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,20 @@ any major contributions.
1212

1313
At first please see the [Get started](../get_started/index.md) section of the documentation to setup the environment.
1414

15+
## How to
16+
17+
If you are a collaborator:
18+
19+
- Make a new branch with `feat/`, `fix/` or `refactor/` prefix. For example: `fix/blocks_cutting`.
20+
- After changes make a PR to develop. Please, don't work on the same branch after the changes are merged.
21+
- Make sure that there are no merge conflicts. If there are some, please, merge the `develop` into your branch first.
22+
23+
If you are not a collaborator:
24+
25+
- Make a fork from `develop` branch.
26+
- After changes, make a PR to from `your:develop` to `blocksnet:develop`.
27+
- Make sure that there are no merge conflicts. If there are some, please, merge the `develop` into your branch first.
28+
1529
## Before submitting your pull request
1630

1731
Before you submit a pull request for your contribution, please work

0 commit comments

Comments
 (0)