mirror of
https://github.com/fleetdm/fleet
synced 2026-05-15 21:18:29 +00:00
handles the edge case mentioned in QA Notes #27689 and - Use consistent *int64 for TeamID across all policy activity types - Fix JSON omitempty issue causing team_id: 0 to be omitted(to fix a small copy test bug in Frontend) ## Testing - [x] Added/updated automated tests - [x] QA'd all new/changed functionality manually Current Output <img width="639" height="166" alt="image" src="https://github.com/user-attachments/assets/ee17b3ee-65c9-430f-ae3b-3c350f7e20f9" /> <img width="647" height="524" alt="image" src="https://github.com/user-attachments/assets/9bc01988-ccca-4ea4-84bf-3a15f35ba428" /> --------- Co-authored-by: Scott Gress <scottmgress@gmail.com> |
||
|---|---|---|
| .. | ||
| adr | ||
| architecture | ||
| assets | ||
| getting-started | ||
| guides | ||
| product-groups | ||
| reference | ||
| research | ||
| responsibilities | ||
| rituals | ||
| workflows | ||
| README.md | ||
Fleet Contributor Documentation
Welcome to the Fleet contributor documentation! This documentation is designed to help you contribute to the Fleet project.
Documentation structure
The documentation is organized into the following sections:
- Getting Started - Setup, building, and testing Fleet
- Guides - How-to guides for common tasks
- Architecture - High-level architecture documentation
- Product Groups - Documentation for specific product groups
- Workflows - Development workflows
- Reference - API reference, configuration, etc.
- ADRs - Architectural Decision Records
- Research - Research documents for product groups
- Responsibilities - Responsibility documents for product groups
Product groups
Fleet is organized into three main product groups:
- MDM - Mobile Device Management
- Orchestration - Device orchestration using osquery
- Software - Software inventory, vulnerability management, and software installation
Contributing
If you're new to Fleet, we recommend starting with the Getting Started section to set up your development environment.
Once you're set up, you can explore the Guides section to learn how to contribute to specific areas of the project.
Architectural Decision Records (ADRs)
We use Architectural Decision Records to document significant architectural decisions. If you're making a significant architectural change, please create an ADR to document your decision.