Thank you for contributing to ScheduleGate! This document outlines how to report bugs, submit pull requests, and maintain code quality.
Open an issue on GitHub with:
- ScheduleGate version (
schedulegate --version) - Operating system and architecture
- Sample schedule file (if possible)
- Expected vs. actual behavior
- Fork the repository and create a branch off
main - Make your changes
- Run
go test ./...— all tests must pass - Submit a pull request with a clear description of the change
- Follow existing patterns in
internal/andcmd/ - Minimalist, direct style — avoid unnecessary comments
- Use descriptive variable names
- Keep functions focused and small
- Add tests for new features
- Maintain the 55% minimum coverage gate
- Run
go test ./... -coverprofile=/tmp/coverage.outto check coverage
# macOS (default)
make build
# Windows
make build-windows
# Linux
make build-linux
# All platforms
make build-allOpen an issue for discussion before starting large changes.