Current Dev Branch: new_classifer
- This is a repo with multiple people working on it. Please develop on your own branch and then merge into the current dev branch
- Please test your code before committing. This is how bugs propogate.
- Please format your code with black.
- Assign yourself an issue
- please do this
- I dont want to overlap on issues and commit on the same things
- Make a branch for that issue
- if you develop on the current dev branch, I will find you
- Work on that branch
- To create a new feature the process of adding it to the workflow is simple
- Create a config for it using the
config/base_config.pyas a base class - Add the config name to
config/pipelinesetup.py - Add config class to
config/pomelo.py - Add function to
drivers/pomelodriver.py
- Create a config for it using the
- If its a smaller change than use your best judgement
- To create a new feature the process of adding it to the workflow is simple
- Add tests if need be
- Test your code once finished
- Ask for a merge req
- DO NOT I REPEAT DO NOT MERGE WITHOUT A SECOND SET OF EYES
- After the approval process merge it right in!
- Repeat
- This is very important. Please test your code that you changed before adding it to the repo
- If you add something with deterministic outputs, write a regular unit test
- If you add something with more random outputs, check that all the steps complete with a test (check if not None or the length)