5
5
.. highlightlang :: python
6
6
7
7
8
-
8
+ ============================================
9
9
Welcome to BrowserMob Proxy's documentation!
10
10
============================================
11
11
12
12
Python client for the BrowserMob Proxy 2.0 REST API.
13
13
14
+ --------------
14
15
How to install
15
16
--------------
16
17
@@ -30,6 +31,7 @@ Then install it by running::
30
31
31
32
$ python setup.py install
32
33
34
+ ----------------------------------
33
35
How to use with selenium-webdriver
34
36
----------------------------------
35
37
@@ -53,6 +55,43 @@ Manually::
53
55
server.stop()
54
56
driver.quit()
55
57
58
+ -----------------
59
+ How to Contribute
60
+ -----------------
61
+
62
+ Getting Started
63
+ ---------------
64
+
65
+ * Fork the repository on GitHub - well... duh :P
66
+ * Create a virtualenv: `virtualenv venv `
67
+ * Activate the virtualenv: `. venv/bin/activate `
68
+ * Install the package in develop mode: `python setup.py develop `
69
+ * Install requirements: `pip install -r requirements.txt `
70
+ * Run the tests to check that everything was successful: `py.test tests
71
+
72
+ Making Changes
73
+ --------------
74
+
75
+ * Create a topic branch from where you want to base your work.
76
+ * This is usually the master branch.
77
+ * Only target release branches if you are certain your fix must be on that
78
+ branch.
79
+ * To quickly create a topic branch based on master; `git checkout -b
80
+ /my_contribution master`. Please avoid working directly on the
81
+ `master ` branch.
82
+ * Make commits of logical units.
83
+ * Check for unnecessary whitespace with `git diff --check ` before committing.
84
+ * Make sure you have added the necessary tests for your changes.
85
+ * Run _all_ the tests to assure nothing else was accidentally broken.
86
+
87
+ Submitting Changes
88
+ ------------------
89
+
90
+ * Push your changes to a topic branch in your fork of the repository.
91
+ * Submit a pull request to the main repository
92
+ * After feedback has been given we expect responses within two weeks. After two
93
+ weeks will may close the pull request if it isn't showing any activity
94
+
56
95
Contents:
57
96
58
97
.. toctree ::
0 commit comments