-
Notifications
You must be signed in to change notification settings - Fork 22
Code management practices
Alex Richert edited this page Oct 15, 2025
·
1 revision
- All work is described in issues.
- All PRs (apart from CI) have an accompanying issue.
- All non-CI related issues should be associated with a release project.
- Releases are published with GitHub release tags. Release descriptions do not need to include purely CI-related changes.
- Issues are for discussing, prioritizing, planning, clarifying, and scheduling work. Issues are not discussed over email or other channels unless specifically needed in order to protect sensitive information (API keys, etc.).
- Issues provide a record of decision making, technical information, and other details useful for later examination.
- Issues should be assigned as soon as needed based on prioritization. An issue that is being actively worked should be assigned to whomever is working on it.
- Labels may be used to establish priority, associate related issues, etc.