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
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ crytic-compile uses the pull request contribution model. Please make an account
14
14
15
15
Some pull request guidelines:
16
16
17
-
- Work from the [`dev`](https://github.com/crytic/crytic-compile/tree/dev) branch. We performed extensive tests prior to merging anything to `master`, working from `dev` will allow us to merge your work faster.
17
+
- Work from the [`dev`](https://github.com/crytic/crytic-compile/tree/dev) branch. We perform extensive tests prior to merging anything to `master`, working from `dev` will allow us to merge your work faster.
18
18
- Minimize irrelevant changes (formatting, whitespace, etc) to code that would otherwise not be touched by this patch. Save formatting or style corrections for a separate pull request that does not make any semantic changes.
19
19
- When possible, large changes should be split up into smaller focused pull requests.
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.
@@ -35,7 +35,7 @@ To run them locally:
35
35
-`darglint crytic_compile`
36
36
37
37
38
-
We use pylint `2.8.2`, black `20.8b1`, mypy `0.812` and dargling`1.8.0`.
38
+
We use pylint `2.12.2`, black `21.10b0`, mypy `0.812` and darglint`1.8.0`.
39
39
40
40
## Development Environment
41
41
Instructions for installing a development version of crytic-compile can be found in our [wiki](https://github.com/crytic/crytic-compile/wiki/Developer-installation).
0 commit comments