Getting started
Fork and clone the repository
Fork the repository on GitHub, then clone your fork locally and add the upstream remote.
Set up your development environment
Choose your preferred setup method.
- Local setup
- Dev Container
Make your changes
- Write clean, modular code.
- Follow PEP 8 style guidelines.
- Add tests for any new functionality.
Commit your changes
Emergent uses Conventional Commits. Format your commit messages as:
Examples:
| Type | Description |
|---|---|
feat | New feature |
fix | Bug fix |
docs | Documentation changes only |
refactor | Code change that neither fixes a bug nor adds a feature |
test | Adding or updating tests |
chore | Maintenance tasks, dependency updates |
build | Changes affecting the build system |
ci | Changes to CI/CD configuration |
Push and open a pull request
Push your branch to your fork, then open a pull request against the main repository.
- Go to github.com/delphilos/emergent.
- Click Pull requests > New pull request.
- Select your fork and branch.
- Provide a detailed description of what you changed and why.
Keep your fork up to date. Before starting new work, sync your fork with upstream to avoid merge conflicts.
Documentation
Emergent maintains two layers of documentation:- Internal docs — docstrings and module
READMEfiles co-located with the source code insrc/. - External docs — Markdown files in the
docs/directory.
- Use simple, direct language.
- Include working code examples.
- Document new features in both the docstring and the external docs.
- Use consistent formatting with existing pages.