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
+6-5
Original file line number
Diff line number
Diff line change
@@ -7,11 +7,11 @@ We love your input! We want to make contributing to this project as easy and tra
7
7
- Proposing new features
8
8
- Becoming a maintainer
9
9
10
-
## We Develop with Github
10
+
## We Develop with GitHub
11
11
We use github to host code, to track issues and feature requests, as well as accept pull requests.
12
12
13
-
## We Use [Github Flow](https://guides.github.com/introduction/flow/index.html), So All Code Changes Happen Through Pull Requests
14
-
Pull requests are the best way to propose changes to the codebase (we use [Github Flow](https://guides.github.com/introduction/flow/index.html)). We actively welcome your pull requests:
13
+
## We Use [GitHub Flow](https://guides.github.com/introduction/flow/index.html), So All Code Changes Happen Through Pull Requests
14
+
Pull requests are the best way to propose changes to the codebase (we use [GitHub Flow](https://guides.github.com/introduction/flow/index.html)). We actively welcome your pull requests:
15
15
16
16
1. Fork the repo and create your branch from `master`.
17
17
2. If you've added code that should be tested, add tests.
@@ -22,8 +22,8 @@ Pull requests are the best way to propose changes to the codebase (we use [Githu
22
22
## Any contributions you make will be under the BSD-2-Clause Software License
23
23
In short, when you submit code changes, your submissions are understood to be under the same [BSD-2-Clause License](https://choosealicense.com/licenses/bsd-2-clause/) that covers the project. Feel free to contact the maintainers if that's a concern.
24
24
25
-
## Report bugs using Github's [issues](https://github.com/briandk/transcriptase-atom/issues)
26
-
We use GitHub issues to track public bugs. Report a bug by [opening a new issue](); it's that easy!
25
+
## Report bugs using GitHub's [issues](https://github.com/Pennyw0rth/NetExec/issues)
26
+
We use GitHub issues to track public bugs. Report a bug by [opening a new issue](https://github.com/Pennyw0rth/NetExec/issues/new/choose); it's that easy!
27
27
28
28
## Write bug reports with detail, background, and sample code
29
29
@@ -43,6 +43,7 @@ People *love* thorough bug reports. I'm not even kidding.
43
43
[PEP](https://peps.python.org/pep-0008/) is used in this project
44
44
45
45
* 4 spaces for indentation rather than tabs
46
+
* Double quotes on outside of strings
46
47
* We use Ruff as linter, there is a VS-Code extension available you can use
0 commit comments