1 # How to develop on this project
3 network_generation welcomes contributions from the community.
7 This instructions are for linux base systems. (Linux, MacOS, BSD, etc.)
8 ## Setting up your own fork of this repo.
12 git clone "https://gerrit.o-ran-sc.org/r/oam" && (cd "oam" && mkdir -p `git rev-parse --git-dir`/hooks/ && curl -Lo `git rev-parse --git-dir`/hooks/commit-msg https://gerrit.o-ran-sc.org/r/tools/hooks/commit-msg && chmod +x `git rev-parse --git-dir`/hooks/commit-msg)
14 - Enter the directory `cd oam/code/network-generation`
15 - Please see [O-RAN-SC Code Contributions Tutorial](https://wiki.o-ran-sc.org/display/ORAN/Tutorial%3A+Making+code+contributions+to+O-RAN+open+source+project)
24 ## Setting up your own virtual environment
26 Run `make virtualenv` to create a virtual environment.
27 then activate it with `source .venv/bin/activate`.
29 ## Install the project in develop mode
31 Run `make install` to install the project in develop mode.
33 ## Run the tests to ensure everything is working
35 Run `make test` to run the tests.
37 ## Create a new branch to work on your contribution
39 Run `git checkout -b my_contribution`
43 Edit the files using your preferred editor. (we recommend VIM or VSCode)
47 Run `make fmt` to format the code.
51 Run `make lint` to run the linter.
55 Run `make test` to run the tests.
57 Ensure code coverage report shows `100%` coverage, add tests to your PR.
59 ## Build the docs locally
61 Run `make docs` to build the docs.
63 Ensure your new changes are documented.
65 ## Commit your changes
67 This project uses [conventional git commit messages](https://www.conventionalcommits.org/en/v1.0.0/).
69 Example: `fix(package): update setup.py arguments 🎉` (emojis are fine too)
71 ## Push your changes to your fork
73 Run `git push origin my_contribution`
75 ## Submit a pull request
77 On github interface, click on `Pull Request` button.
79 Wait CI to run and one of the developers will review your PR.
82 This project comes with a `Makefile` that contains a number of useful utility.
89 help: ## Show the help.
90 install: ## Install the project in dev mode.
91 fmt: ## Format code using black & isort.
92 lint: ## Run pep8, black, mypy linters.
93 test: lint ## Run tests and generate coverage report.
94 watch: ## Run tests on every change.
95 clean: ## Clean unused files.
96 virtualenv: ## Create a virtual environment.
97 release: ## Create a new tag for release.
98 docs: ## Build the documentation.
99 switch-to-poetry: ## Switch to poetry package manager.
100 init: ## Initialize the project based on an application template.
103 ## Making a new release
105 This project uses [semantic versioning](https://semver.org/) and tags releases with `X.Y.Z`
106 Every time a new tag is created and pushed to the remote repo, github actions will
107 automatically create a new release on github and trigger a release on PyPI.
109 For this to work you need to setup a secret called `PIPY_API_TOKEN` on the project settings>secrets,
110 this token can be generated on [pypi.org](https://pypi.org/account/).
112 To trigger a new release all you need to do is.
114 1. If you have changes to add to the repo
115 * Make your changes following the steps described above.
116 * Commit your changes following the [conventional git commit messages](https://www.conventionalcommits.org/en/v1.0.0/).
117 2. Run the tests to ensure everything is working.
118 4. Run `make release` to create a new tag and push it to the remote repo.
120 the `make release` will ask you the version number to create the tag, ex: type `0.1.1` when you are asked.
122 > **CAUTION**: The make release will change local changelog files and commit all the unstaged changes you have.