This section covers the end-to-end development workflow for PLESTY modules. From branching conventions through CI/CD to publishing, you'll learn how to contribute code that meets PLESTY's quality standards.
The development cycle
- Branch — create a feature branch from
exp - Implement — write your code following PLESTY conventions
- Check — run
plesty checkto pass all quality gates - Commit — commit with a conventional commit message
- Push — push to
exp(feature branch merges intoexp) - CI — the pipeline runs automatically
- Release — tag and publish
Sections
| Page | Description |
|---|---|
| Branch Discipline | Branching rules for core and hub repositories |
| CI Pipeline | Setting up and understanding the CI pipeline |
| Publishing | Tagging and publishing packages to PyPI |
Key principles
- Never push directly to
main— all changes go throughexp - Always branch from
exp— never frommain - Run checks before pushing — use
plesty check --standard nebulaat minimum - Use conventional commits —
feat:,fix:,docs:, etc.
Next steps
- Learn about branch discipline
- Set up the CI pipeline
- Publish your module