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: docs/contributing.rst
+8-6Lines changed: 8 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,13 +13,15 @@ Code
13
13
#. Fork the repository `sftpretty <https://github.com/byteskeptical/sftpretty>`_
14
14
#. Install supporting software packages and sftpretty in --editable mode
15
15
16
-
a. Make a virtualenv, clone the repos, install the deps from pip install -r requirements-dev.txt
17
-
b. Install sftpretty in editable mode, pip install -e .
16
+
a. Make a virtualenv, python3 -m venv .sftpretty
17
+
b. Clone the repo, git clone https://github.com/`username`/sftpretty
18
+
c. Install sftpretty and it's dependencies in editable mode, python3 -m pip install -e .[dev,lint,test]
19
+
18
20
#. Write any new tests needed and ensure existing tests continue to pass without modification.
19
21
20
-
a. Setup CI testing for your Fork. Currently testing is done on Github Actions but feel free to use the testing framework of your choosing.
21
-
b. Testing features that concern chmod, chown on Windows is NOT supported. Testing compression has to be ran against a local compatible sshd and not the plugin as it does NOT support this test.
22
-
c. You will need to setup an ssh daemon on your local machine and create a user: copy the contents of id_sftpretty.pub to the newly created user's authorized_keys file -- Tests that can only be run locally are skipped using the @skip_if_ci decorator so they don't fail when the test suite is run on the CI server.
22
+
a. Setup CI testing for your fork. Currently testing is done on Github Actions but feel free to use the framework of your choosing.
23
+
b. Testing features that concern chmod, chown on Windows is NOT supported. Testing compression has to be ran against a local compatible sshd and not the pytest-sftpserver plugin as it does NOT support this feature.
24
+
c. You will need to setup an ssh daemon on your local machine and create a user: copy the contents of id_sftpretty.pub to the newly created user's authorized_keys file -- Tests that can only be ran locally are skipped using the @skip_if_ci decorator so they don't fail when the test suite runs on the CI server.
23
25
24
26
#. Ensure that your name is added to the end of the :doc:`authors` file using the format Name <email@domain.com> (url), where the (url) portion is optional.
25
27
#. Submit a Pull Request to the project.
@@ -40,4 +42,4 @@ This section lists the priority that will be assigned to an issue:
40
42
41
43
Testing
42
44
-------
43
-
Tests specific to an issue should be put in the tests/ directory and the module should be named test_issue_xx.py The tests within that module should be named test_issue_xx or test_issue_xx_YYYYYY if more than one test. Pull requests should not modify existing tests (exceptions apply). See tests/test_issue_xx.py for a template and further explanation.
45
+
Tests specific to an issue should be placed inside the tests/ directory and the file should be named test_issue_xx.py. The tests within that module should be named test_issue_xx or test_issue_xx_YYYYYY if more than one test exists. Pull requests should not modify existing tests with extremely rare exception. See tests/test_issue_xx.py for a template and additional context.
0 commit comments