@@ -6,7 +6,8 @@ Scarb is actively developed and open for contributions!
6
6
Grab any unassigned issue labeled with [ ` help-wanted ` ] ( https://github.com/software-mansion/scarb/labels/help%20wanted ) !
7
7
8
8
* Looking for some easy warmup tasks?*
9
- Check out issues labeled with [ ` good-first-issue ` ] ( https://github.com/software-mansion/scarb/labels/good%20first%20issue ) !
9
+ Check out issues labeled with [
10
+ ` good-first-issue ` ] ( https://github.com/software-mansion/scarb/labels/good%20first%20issue ) !
10
11
11
12
* Need some guidance?*
12
13
Reach out to other developers on [ Telegram] ( https://t.me/+1pMLtrNj5NthZWJk ) !
@@ -17,7 +18,8 @@ Latest stable Rust is the only thing you really need.
17
18
It is recommended to use [ rustup] ( https://rustup.rs/ ) for getting it.
18
19
19
20
If you wish to work on Scarb's website, you will need [ Node.js] ( https://nodejs.org/ ) .
20
- We recommend to install it using [ asdf] ( https://asdf-vm.com/ ) (via [ nodejs] ( https://github.com/asdf-vm/asdf-nodejs ) plugin).
21
+ We recommend to install it using [ asdf] ( https://asdf-vm.com/ ) (via [ nodejs] ( https://github.com/asdf-vm/asdf-nodejs )
22
+ plugin).
21
23
22
24
## Contributing
23
25
@@ -56,13 +58,31 @@ Each commit should pass lints and tests.
56
58
Then, set up a stack of pull requests, separate PR for each commit, and pointing to the previous one.
57
59
58
60
While your PR is being reviewed on, you can push merge commits and
59
- use [ ` git commit --fixup ` ] ( https://git-scm.com/docs/git-commit/2.32.0#Documentation/git-commit.txt---fixupamendrewordltcommitgt )
61
+ use [
62
+ ` git commit --fixup ` ] ( https://git-scm.com/docs/git-commit/2.32.0#Documentation/git-commit.txt---fixupamendrewordltcommitgt )
60
63
to push further changes to your commits.
61
64
62
65
### Typos
66
+
63
67
Our policy is to not accept PRs that only fix typos in the documentation and code. We appreciate your effort, but we
64
68
encourage you to focus on bugs and features instead.
65
69
70
+ ## Tips
71
+
72
+ ### Testing custom Cairo compiler changes
73
+
74
+ Sometimes you may happen to work on a feature to the Cairo compiler, and you would like to test how it works in Scarb
75
+ (for example, if you are working on Starknet Foundry).
76
+
77
+ We have a script that edits the ` Cargo.toml ` file to use a local checkout of the Cairo compiler.
78
+ To use this tool, run:
79
+
80
+ ``` shell
81
+ cargo xtask set-cairo-version --path ../path/to/cairo
82
+ ```
83
+
84
+ And then you can ` cargo build ` Scarb with your custom Cairo compiler changes.
85
+
66
86
---
67
87
68
88
Thanks! ❤️ ❤️ ❤️
0 commit comments