The scc command provides tools for simplifying the Git(Hub) workflow.
Direct dependencies of scc are:
To install scc, run:
$ python setup.py installor using pip, run:
$ pip install sccTo upgrade your pip installation, run:
$ pip install -U sccThe list of available commands can be listed with:
$ scc -hFor each subcommand, additional help can be queried, e.g.:
$ scc merge -hPyGithub follows PEP 8, the Style Guide for Python Code. Please check your code with pep8 or flake8, the Python style guide checkers, by running flake8 -v . or pep8 -v ..
The tests are located under the test directory. To run all the tests, use the test target of `setup.py`:
python setup.py testUnit tests are stored under the test/unit folder and can be run by calling:
python setup.py test -t test/unitUnit tests are also run by the Travis build on every Pull Request opened against the main repository.
Integration tests are stored under test/integration. Many integration tests use snoopys-sandbox and snoopys-sandbox-2 as sandbox repositories to test the scc commands.
Running the integration test suite requires:
- a GitHub account
a token-based GitHub connection, i.e. a global
github.tokenstored under the global Git configuration file:$ git config --global github.token xxxx- the user authenticated by the token defined above needs to own forks of snoopys-sandbox and snoopys-sandbox-2
Once this is set up, the integration tests can be run by calling:
python setupy.py test -s test/integrationIntegration tests are run daily on the OME Continuous Integration infrastructure under the SCC-self-merge job using the token-authenticated snoopycrimecop user
snoopycrimecop is released under the GPL.
2012-2016, The Open Microscopy Environment
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent