fleet/docs/Contributing
Dhruv Trivedi 431decc3ce
fix: standardize team_id handling in policy activities (#32151)
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>
2025-08-27 08:43:36 -05:00
..
adr ADR-0005: Standardize on OpenTelemetry for observability (#31864) 2025-08-18 18:31:24 -05:00
architecture Fix a few broken references (#31640) 2025-08-21 12:13:45 -05:00
assets SCIM Entra ID support (#28832) 2025-05-08 13:02:49 -05:00
getting-started Running Fleet locally: Building MDM features (#31829) 2025-08-13 09:27:27 -05:00
guides Update design-qa-considerations.md (#31837) 2025-08-13 09:31:53 -05:00
product-groups 31167: SUSP api (#32163) 2025-08-26 11:31:06 -04:00
reference fix: standardize team_id handling in policy activities (#32151) 2025-08-27 08:43:36 -05:00
research Lightweight push notification simulator (SSE-based) (#31310) 2025-07-29 07:29:56 +02:00
responsibilities Organize contributor docs and establish ADR process and template (#29101) 2025-05-17 15:03:52 -05:00
rituals Adding stub for additional ritual documentation to help add clarity but not overwhelm the handbook with too many details (#31872) 2025-08-25 13:52:53 -05:00
workflows Update release notes template (#31014) 2025-07-23 12:05:10 -06:00
README.md Update contrib docs headers to sentence case (#29276) 2025-05-20 11:26:35 -05:00

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:

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.