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
Bug reports and feature suggestions can be submitted to our issue tracker. For bug reports, attaching the contract that caused the bug will help us in debugging and resolving the issue quickly. If you find a security vulnerability, do not open an issue; email [email protected] instead.
8
8
9
9
## Questions
10
10
Questions can be submitted to the issue tracker, but you may get a faster response if you ask in our [chat room](https://slack.empirehacking.nyc/) (in the #ethereum channel).
11
11
12
-
## Code
12
+
## Code
13
13
solc-select uses the pull request contribution model. Please make an account on Github, fork this repo, and submit code contributions via pull request. For more documentation, look [here](https://guides.github.com/activities/forking/).
14
14
15
15
Some pull request guidelines:
@@ -20,31 +20,87 @@ Some pull request guidelines:
20
20
- Fill out the pull request description with a summary of what your patch does, key changes that have been made, and any further points of discussion, if applicable.
21
21
- Title your pull request with a brief description of what it's changing. "Fixes #123" is a good comment to add to the description, but makes for an unclear title on its own.
22
22
23
-
## Linters
23
+
## Development Setup
24
24
25
-
Several linters and security checkers are run on the PRs.
25
+
### Setting up the Development Environment
26
26
27
-
To run them locally in the root dir of the repository:
27
+
#### Using uv (recommended - fastest)
28
28
29
-
-`pylint solc_select --rcfile pyproject.toml`
30
-
-`black . --config pyproject.toml`
31
-
32
-
We use pylint `2.8.2` black `20.8b1`.
33
-
34
-
## Running Tests
35
-
36
-
These tests can be run locally by using the `bash test_{linux | macos | windows}.sh` respective scripts.
0 commit comments