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
Generally <repository-alias-name> is named origin, but in the case of multiple fetch/pull source of repository you can choose whatever name you want
121
-
121
+
122
122
3. Create a branch for local development::
123
123
124
124
git checkout -b name-of-your-bugfix-or-feature
125
-
125
+
126
126
4. Check out the Contributing to Code Development `documentation <https://scancode-toolkit.readthedocs.io/en/stable/contribute/contrib_dev.html>`_, as it contains more in-depth guide for contributing code and documentation.
127
127
128
128
5. To configure your local environment for development, locate to the main
129
129
directory of the local repository, and run the configure script.
130
130
The configure script creates an isolated Python `virtual environment` in
131
131
your checkout directory, the Python `pip` tool, and installs the third-party
132
132
libraries (from the `thirdparty/ directory`), setup the paths, etc.
133
-
See https://virtualenv.pypa.io/en/latest/ for more details.
133
+
See https://virtualenv.pypa.io/en/latest/ for more details.
134
134
135
135
Run this command to configure ScanCode::
136
136
@@ -160,15 +160,17 @@ To set up ScanCode for local development:
160
160
6. Now you can make your code changes in your local clone.
161
161
Please create new unit tests for your code. We love tests!
162
162
163
-
7. An update to the ``CHANGELOG`` is required if any important changes are made that needs to be communicated such as:
163
+
7. An update to the ``CHANGELOG`` is required if any important changes are made
164
+
that needs to be communicated such as:
164
165
165
166
* Changes in the API.
166
167
167
168
* Addition or deletion of CLI options.
168
169
169
170
* Addition of any new feature or any other miscellaneous changes to the program.
170
-
171
-
8. If there is a code change, a significant document, or any other changes, you must update the ``AUTHORS`` to include your own name.
171
+
172
+
8. If there is a code change, a significant document, or any other changes,
173
+
you must update the ``AUTHORS`` to include your own name.
172
174
173
175
9. When you are done with your changes, run all the tests.
0 commit comments